system and method to enable low latency and reliable communication

专利摘要:
A system and method for multiplexing traffic. A wireless device such as user equipment (UE) can receive a first signal on first resources assigned to carry a first downlink transmission from a base station, and receive a first downlink control indication message. (DCI) from the base station. The first DCI message can include a preemption region (PR) indication and a PR bitmap, and the PR indication can indicate a location of a time-frequency region. The PR bitmap can include bits associated with different portions of the time-frequency region, and each of the bits in the PR bitmap can indicate whether a preemptive downlink transmission is present in the corresponding portion of the time region. -frequency.
公开号:BR112020002686A2
申请号:R112020002686-7
申请日:2018-08-09
公开日:2020-07-28
发明作者:Toufiqul Islam；Amine Maaref；Yongxia Lyu
申请人:Huawei Technologies Co., Ltd.；
IPC主号:

专利说明:

[0001] [0001] This application claims priority to Patent Application No. US15 / 925,452, filed on March 19, 2018, entitled “System and Method for Enabling Reliable and Low Latency Communication”, and to Provisional Patent Application No. US62 / 543,825, filed on August 10, 2017, entitled “System and Method for Enabling Reliable and Low Latency Communication”, the content of which is incorporated by reference in this document as if reproduced in its entirety. TECHNICAL FIELD
[0002] [0002] The present invention relates, in general, to the management of the allocation of resources in a network and, in particular modalities, to techniques and mechanisms for a system and method to enable reliable and low latency communication. BACKGROUND
[0003] [0003] In some wireless communication systems, a user equipment (UE) communicates wirelessly with one or more base stations. A wireless communication from a UE to a base station is called an uplink communication. A wireless communication from a base station to a UE is called a downlink communication. The resources are necessary to carry out uplink and downlink communications. For example, a base station or group of base stations can wirelessly transmit data to a UE in a downlink communication at a particular frequency for a particular duration of time. The frequency and duration of time are examples of resources.
[0004] [0004] A base station allocates resources for downlink communications with the UEs served by the base station. Wireless communications can be carried out by transmitting orthogonal frequency division (OFDM) multiplexing symbols.
[0005] [0005] Some UEs served by a base station may need to receive data from the base station with lower latency than other UEs served by the base station. For example, a base station can serve multiple UEs, including a first UE and a second UE. The first UE can be a mobile device carried by a human being who is using the first UE to browse the Internet. The second UE can be equipment in an autonomous vehicle that moves on a motorway. Although the base station is serving the two UEs, the second UE may need to receive data with lower latency when compared to the first UE. The second UE may also need to receive its data more reliably than the first UE. The second UE can be an ultra-reliable, low-latency communication UE (URLLC), while the first UE can be an enhanced mobile broadband UE (eMBB).
[0006] [0006] UEs that are served by a base station and that require lower latency downlink communication will be referred to as "low latency UEs". The other UEs served by the base station will be called “latency tolerant UEs”. The data to be transmitted from the base station to a low latency UE will be called "low latency data", and the data to be transmitted from the base station to a latency tolerant UE will be called "latency tolerant data".
[0007] [0007] In some situations, a programmed latency-tolerant transmission may need to be fully or partially preempted in favor of a lower latency transmission in order to satisfy the latency constraint of the lower latency transmission. There is a desire for an improved method of communicating, with the receiver of the lowest latency transmission, that its transmission has been subjected to preemption. SUMMARY OF THE INVENTION
[0008] [0008] The technical advantages are achieved, in general, through modalities of this disclosure that describe a system and method to enable reliable and low latency communication.
[0009] [0009] In accordance with one modality, a method for wireless communications is provided, as can be done using user equipment (UE). In this example, the method includes receiving a first signal through the first resources allocated to carry a first downlink transmission from a base station. The method additionally includes receiving a first downlink control indication (DCI) message from the base station. The first DCI message includes a preemption region (PR) indication and a PR bitmap, the PR indication indicates a location of a time-frequency region, and the PR bitmap includes bits associated with different portions of the time-frequency region. Each of the bits in the PR bitmap indicates whether a preemptive downlink transmission is present in the corresponding portion of the time-frequency region. An apparatus for carrying out this method is also provided. In one example, the time-frequency region associated with the PR indication is a sub-region of a pre-configured time-frequency region. In such an example, the PR bitmap includes a fixed number of bits and the time-frequency region associated with the PR indication is smaller than the pre-configured time-frequency region, thereby increasing the granularity in that the PR bitmap identifies preemptive downlink transmissions. In this example, or another example, the indication of PR indicates a starting location or ending location of the time-frequency region. Optionally, in any of the preceding examples, or in another example, the indication of PR indicates an initial frequency or final frequency of the time-frequency region. Optionally, in any of the preceding examples, or in another example, the indication of PR indicates a duration of the time-frequency region in the time domain.
[0010] [0010] Optionally, in any of the preceding examples, or in another example, the PR indication field indicates a bandwidth of the time-frequency region. Optionally, in either of the preceding examples, or in another example, the first DCI message additionally includes a bitmap configuration of the PR bitmap, the bitmap configuration identifying a number of bits, in the PR bitmap, which is mapped to different time domain resources of the time-frequency region and a number of bits, in the PR bitmap field, which is mapped to different domain resources of frequency of the time-frequency region.
[0011] [0011] Optionally, in any of the preceding examples, or in another example, the method additionally comprises receiving a second signal through resources assigned to carry a second downlink transmission from the base station, and receive a second DCI message from the base station. The second DCI message includes a PR indication that indicates a location of a second time-frequency region, where the second time-frequency region has a different duration or bandwidth than the time-frequency region. Optionally, in any of the preceding examples, or in another example, the PR indication field and the PR bitmap field, in the first DCI message, are UE-specific fields. Optionally, in any of the preceding examples, or in another example, the PR indication field and the PR bitmap field, in the first DCI message, are group-specific fields. Optionally, in either of the preceding examples, or in another example, the first DCI message is received after the first transmission.
[0012] [0012] In accordance with one modality, a method for wireless communications is provided, as can be done through a base station (BS). In this example, the method includes transmitting a first signal through the first resources assigned to carry a first downlink transmission to user equipment (UE). The method additionally includes transmitting a first downlink control indication (DCI) message to the UE. The first DCI message includes a preemption region (PR) indication and a PR bitmap, the PR indication indicates a location of a time-frequency region, and the PR bitmap includes bits associated with different portions of the time-frequency region. Each of the bits in the PR bitmap indicates whether a preemptive downlink transmission is present in the corresponding portion of the time-frequency region. An apparatus for carrying out this method is also provided. In one example, the time-frequency region is determined based on preemptive downlink transmission. In this example, or another example, the time-frequency region associated with the PR indication is a sub-region of a pre-configured time-frequency region. In such an example, the PR bitmap includes a fixed number of bits and the time-frequency region associated with the PR indication is smaller than the pre-configured time-frequency region, thereby increasing the granularity in that the PR bitmap identifies preemptive downlink transmissions.
[0013] [0013] Optionally, in any of the preceding examples, or in another example, the indication of PR indicates an initial or final location of the time-frequency region. Optionally, in any of the preceding examples, or in another example, the indication of PR indicates an initial frequency or final frequency of the time-frequency region. Optionally, in any of the preceding examples, or in another example, the indication of PR indicates a duration of the time-frequency region in the time domain. Optionally, in any of the preceding examples, or in another example, the PR indication field indicates a bandwidth of the time-frequency region.
[0014] [0014] Optionally, in any of the preceding examples, or in another example, the first DCI message additionally includes a bitmap configuration of the PR bitmap, the bitmap configuration being identifies a number of bits in the PR bitmap that is mapped to different time domain resources in the time-frequency region and a number of bits in the PR bitmap field that is mapped to different resources frequency domain of the time-frequency region. Optionally, in any of the preceding examples, or in another example, the method further comprises transmitting a second signal through resources assigned to carry a second downlink transmission from the base station, and transmitting a second DCI message from the base station, the second DCI message including a PR indication that indicates a location of a second time-frequency region. The second time-frequency region has a different duration or bandwidth than the time-frequency region.
[0015] [0015] Optionally, in any of the preceding examples, or in another example, the PR indication field and the PR bitmap field, in the first DCI message, are UE-specific fields. Optionally, in any of the preceding examples, or in another example, the PR indication field and the PR bitmap field, in the first DCI message, are group-specific fields. Optionally, in either of the preceding examples, or in another example, the first DCI message is received after the first transmission. BRIEF DESCRIPTION OF THE DRAWINGS
[0016] [0016] For a more complete understanding of the present disclosure and its advantages, reference is now made to the following descriptions obtained in conjunction with the accompanying drawings, in which:
[0017] [0017] Figure 1 illustrates a network for communicating data.
[0018] [0018] Figure 2 illustrates a modality of minislot architecture.
[0019] [0019] Figure 3 illustrates a modality of structure of minislots.
[0020] [0020] Figure 4 illustrates two modalities of initial positions of minislots.
[0021] [0021] Figure 5 illustrates a modality of explicit post-indication of minislot traffic.
[0022] [0022] Figure 6 illustrates a modality flowchart of a communication scheme with indication of low latency traffic.
[0023] [0023] Figure 7 illustrates a modality of structure of a semi-static indicator / indication of preemption (PI).
[0024] [0024] Figure 8 illustrates two types of minislot traffic PIs.
[0025] [0025] Figure 9 illustrates two other modalities of dynamic IPs for minislot traffic.
[0026] [0026] Figure 10 illustrates a modality of construction of group downlink control (DCI) information for preemption indication (PI).
[0027] [0027] Figure 11 illustrates a modality of adaptive notification of a preemption region (PR).
[0028] [0028] Figure 12 illustrates a non-contiguous PR modality.
[0029] [0029] Figure 13 illustrates a common group DCI structure modality (GC DCI).
[0030] [0030] Figure 14 illustrates another modality of adaptive notification structure of a PR.
[0031] [0031] Figure 15 illustrates a modality of UE behavior when monitoring GC DCI with common information.
[0032] [0032] Figure 16 illustrates another modality of UE behavior when monitoring GC DCI with common information.
[0033] [0033] Figure 17 illustrates a modality diagram of a processing system.
[0034] [0034] Figure 18 illustrates a transceiver modality diagram.
[0035] [0035] Figure 19 is a flowchart of modality of a method for a UE to carry out wireless communications.
[0036] [0036] Figure 20 is a mode flowchart of a method for a base station to carry out wireless communications.
[0037] [0037] The corresponding numerals and symbols in the different figures refer, in general, to corresponding parts, unless otherwise indicated. The figures are produced to clearly illustrate the relevant aspects of the modalities and are not necessarily produced in scale. DETAILED DESCRIPTION OF ILLUSTRATIVE MODALITIES
[0038] [0038] The production and use of modalities for this disclosure are discussed in detail below. It should be noted, however, that the concepts revealed in this document can be incorporated in a wide variety of specific contexts, and that the specific modalities discussed in this document are only illustrative and are not intended to limit the scope of the claims. In addition, it should be understood that various changes, substitutions and alterations can be made to this document without departing from the spirit and scope of this disclosure, as defined by the attached claims.
[0039] [0039] Figure 1 illustrates a network 100 for communicating data. Network 100 comprises a base station 110 that has a coverage area 112, a plurality of mobile devices 120 and 140 and a backhaul network 130. As shown, base station 110 establishes uplink connections (dashed line) and / or downlink (dotted line) with mobile devices 120 and 140, which serve to carry data from mobile devices 120 and 140 to base station 110 and vice versa. Data carried over uplink / downlink connections can include data communicated between mobile devices 120 and 140, as well as data communicated to / from a remote end device (not shown) via the backhaul network 130. As used in this document , the term “base station” refers to any component (or collection of components)
[0040] [0040] The mobile device or UE 120 can be a low-latency UE, and the mobile device or UE 140 can be a latency-tolerant UE. That is, UE 120 may require lower latency downlink communication when compared to UE 140. For example, UE 120 may be an UE URLLC, and UE 140 may be an EMBB UE. It should be understood that references to URLLC and eMBB in this disclosure are only examples of low-latency traffic and latency-tolerant traffic, and that the principles described in this document are equally applicable to any two types of traffic (and / or types of traffic). EU) that have different latency requirements. Some examples include low-latency traffic that does not require high reliability and latency-tolerant traffic with less stringent reliability requirements. Some use cases that may have particular latency requirements also include massive machine type (mMTC) and / or narrowband IoT communication. It is understood that the schemes discussed in this document may also refer to the examples mentioned above or other examples, where applicable. Although base station 110 serves only two UEs in Figure 1, in real operation, base station 110 can serve many more UEs. It is also contemplated that a single UE 120, 140 may be served by more than one base station
[0041] [0041] When base station 110 has data to transmit to UEs 120 and / or 140, base station 110 transmits that data in one or more downlink transmissions using allocated resources, for example, time resources /frequency. Specific resource partitions can be assigned for transmissions to UEs 120, 140. A portion of the time / frequency resources can be used for low-latency downlink data transmission (for example, for URLLC UE 120), and this portion can be called low latency resources. Some other portion of the time / frequency resources can be used for downlink transmission of latency-tolerant data (for example, for EMBB UE 140), and that portion can be called latency-tolerant resources. The portion of resources used as low-latency resources can change dynamically or semi-statically over time, for example, based on factors such as traffic load, bandwidth requirements and latency. It is important to note that latency-tolerant resources and low-latency resources are just examples of different types of resources. In general, the principles described in this document can also apply to any two types of resources that can be used for different types of traffic that have different latency or that have different quality of service (QoS) requirements.
[0042] [0042] Low latency data can be intermittent or sporadic in nature, and can be transmitted in small packets. It may be inefficient to devote resources to low-latency data. Therefore, a coexistence region can be defined in which a resource allocation for latency-tolerant traffic overlaps the resource allocation for low-latency traffic in the time and frequency domains. Latency-tolerant UEs can monitor the presence of low-latency traffic during transmission if they are programmed in resources that overlap with the coexistence region. In another example, no specific coexistence region can be reserved. Coexistence can occur dynamically within shared time-frequency resources within a carrier bandwidth (BW). In addition, it is also possible that coexistence resources can span multiple carrier BWs.
[0043] [0043] Existing technologies can use downlink multiplexing (DL) based on indication. Possible signaling solutions for implicit and explicit indications of low latency traffic during and / or after impacted transmission of latency-tolerant traffic may be desirable. The proposed solutions can use latency-tolerant traffic code block interleaving, and latency-tolerant transport block (TB) mapping can also be updated for a better coexistence experience.
[0044] [0044] Low latency resources can be partitioned into transmission time units (TTUs). A TTU of low-latency resources can be called a "low-latency TTU". A TTU can be a unit of time that can be allocated for a particular type of transmission, for example, a low-latency data transmission. The transmission can be scheduled or unscheduled. In some embodiments, a TTU is the smallest unit of time that can be allocated for a transmission of a particular type. In addition, a TTU is sometimes referred to as a transmission time interval (TTI). In other embodiments, a low latency TTU includes an integer number of symbols for a given numerology.
[0045] [0045] Latency-tolerant resources can be partitioned into programming intervals, and a programming interval of latency-tolerant resources can be called a "latency-tolerant UE programming interval". A latency-tolerant UE programming interval is the shortest time interval that can be programmed for a data transmission to a latency-tolerant UE. A latency-tolerant programming interval can also be called a latency-tolerant TTU. A latency-tolerant TTU can cover one or multiple symbols / slots of a given numerology. For example, a latency-tolerant TTU can be 1 ms that consists of 14 symbols based on 15 kHz subcarrier spacing. If a slot is defined as 7 symbols, then, in this example, a latency-tolerant TTU or programming interval covers two slots. A low-latency TTU can have a duration that is shorter than a latency-tolerant TTU. By transmitting short-lived transport blocks (TBs) on low-latency resources, the latency of data transmissions to low-latency UEs can be reduced.
[0046] [0046] In some modalities, low latency resources have a numerology that is different from the numerology of latency-tolerant resources, for example, the subcarrier spacing of low latency resources is different from the subcarrier spacing of latency-tolerant resources. Low-latency resources can have a subcarrier spacing that is greater than the subcarrier spacing of latency-tolerant resources. For example, the subcarrier spacing of low-latency resources can be 60 kHz, and the subcarrier spacing of latency-tolerant resources can be 15 kHz. Using greater subcarrier spacing, the duration of each OFDM symbol on low latency resources may be shorter than the duration of each OFDM symbol on latency-tolerant resources. Latency-tolerant TTUs and low-latency TTUs can include the same number of symbols, or different amounts of symbols. Symbols in latency-tolerant TTUs and low-latency TTUs can have the same numerology, or different numerologies. If a TTU is defined as having a fixed number of OFDM symbols regardless of numerology, then more than one low-latency TTU can be transmitted during a latency-tolerant UE programming interval. For example, the latency-tolerant UE programming interval can be an integer multiple of the low-latency TTU. The symbol length on latency-tolerant TTUs and / or low-latency TTU can vary by changing the length of a cyclic prefix on latency-tolerant TTU and / or low-latency TTU. In other modalities, low-latency resources and latency-tolerant resources have the same numerology. A low-latency TTU can then be set to have fewer OFDM symbols when compared to the number of OFDM symbols in a latency-tolerant UE programming interval, so that there is still more than one low-latency TTU within a latency-tolerant UE programming interval. For example, the duration of a low-latency TTU can be as short as a single OFDM symbol. It is also contemplated that low latency transmission and latency tolerant transmission may not have the same number of symbols per TTU, regardless of whether or not they have the same numerology. If different numerology is used, the symbols of a low-latency TTU can line up in the delimitation of the one or multiple symbols of the latency-tolerant TTU with equal or different CP overloads.
[0047] [0047] A TTU can be divided into several slots, for example, 20 slots. A low-latency slot life can be equal to or shorter than a latency-tolerant slot or a long-term evolution (LTE) slot. A minislot can contain any number of symbols that is less than the number of symbols in a slot, for example, 1, 3, 6 symbols if a slot is 7 symbols.
[0048] [0048] Figure 2 illustrates a minislot architecture modality. In this example, a minislot comprises two symbols. A low-latency TTU can include physical control format indicator (PCFICH) channel or hybrid automatic repeat request indicator (ARQ) physical channel (PHICH). Alternatively, the PCFICH and / or PHICH indicators can be excluded from a low latency TB. Control information for a low latency TTU can be limited to the first symbol. Resource elements (Res) that contain control information for low-latency traffic may or may not be contiguous. The same demodulation reference signal (DMRS) can be used for low-latency control information and data. Since the time domain granularity is short, multiple resource blocks can be grouped together for minimal resource granularity when minislot is programmed. The resource allocation granularity based on resource block group (RBG) can be based on compact downlink control (DCI) information or 1 RBG with minimal granularity.
[0049] [0049] The DMRS can be loaded from the front or distributed over the duration of the minislot. A higher level of aggregation of the control channel element (CCE) in a physical downlink control channel (PDCCH) can be supported, and fewer UEs can be programmed by minislot for more reliability.
[0050] [0050] Figure 3 illustrates a modality of structure of minislots. The low-latency minislot can have a numerology that is different from the numerology of latency-tolerant resources. Low-latency data transmission can be based on a slot or a minislot. For example, the latency-tolerant transmission may be long enough to contain more than one low-latency transmission. Examples of low latency TTU durations and an example of a latency-tolerant UE programming interval are shown. EMBB 302 control information can be reserved at the beginning of a single slot or a set of consecutive slots. A long cyclic prefix (CP) eMBB symbol 304 may be slightly longer than a regular CP eMBB symbol 310; a 306 long CP URLLC symbol can be a little longer than a regular 308 CP URLLC symbol. As shown in Figure 3, a low latency symbol or URLLC symbol may not cover the entire bandwidth of a latency-tolerant symbol or eMBB symbol. In the exemplary time / frequency resources, shown in Figure 3, specific resource partitions are scheduled for transmissions to latency-tolerant UEs and low-latency UEs. However, the illustrated resource partitions are just one example. In addition, in addition to time / frequency resources, other resources can be allocated for transmission to latency-tolerant UEs and low-latency UEs, such as code, power and / or space resources.
[0051] [0051] Figure 4 illustrates two modalities of initial positions of minislots. The minislot's initial position in time and / or frequency domains depends on the frame structure of the slot / TTU used for latency-tolerant transmission. For example, the frame structure consists of a control channel field, a data channel field and a slot pilot field. The initial position of the minislot can be orthogonal to the control channel field and / or pilot field of a slot to avoid degradation of transmission performance in latency-tolerant traffic slots. Depending on whether the 402 latency-tolerant control information comprises one or two symbols, the latency-tolerant control information 401 may not fully occupy the first symbol of a latency-tolerant slot. The minislot 404 can start at the first symbol of a latency-tolerant slot, or the latency-tolerant control and reference signal can fully occupy the first symbol, and minislot 404 can start at the second symbol. Other examples are also possible. For example, a minislot can overlap a boundary between two slots so that it overlaps the last one or more symbols in the previous slot and the first one or more symbols in the subsequent slot. In another modality, a latency-tolerant transmission in progress can be “punctured” by replacing a portion of the latency-tolerant transmission with a low-latency transmission (not shown in Figure 4). Alternatively, instead of puncturing, latency-tolerant transmission and low-latency transmission can be overlaid on the same time-frequency resources, optionally, with a power shift or other method appropriate for each intended receiver to identify and decode corresponding transmission. The signaling methods, described in this document for punctured latency-tolerant TBs, can also be used to indicate overlapping latency-tolerant and low-latency transmissions.
[0052] [0052] While the description below may assume minislot-based transmissions for low-latency traffic, it is envisaged that the methods described in this document may be applicable to other forms or types of low-latency transmissions, including, for example, a minislot or slot or an aggregation of minislots or slots in a numerology.
[0053] [0053] The indication of arrival / presence of low latency traffic can be signaled using the resources normally reserved for control signaling in any of the types of transmission, or by transmitting additional control signaling within the resources that would be allocated , otherwise, for data within the latency-tolerant transmission. For example, different control messages can be used to indicate low-latency and latency-tolerant traffic when low-latency traffic (for example, URLLC traffic) arrives. Alternatively, a single control message can be used to indicate low latency traffic and latency-tolerant traffic at the end of a latency-tolerant UE programming interval. Signaling for low-latency traffic can be either explicit or implicit. For explicit indication, some REs (for example, contained within a symbol or that span multiple contiguous or non-contiguous symbols)
[0054] [0054] Alternatively, one or more REs of eMBB symbols at the end of an eMBB / TTU interval can be used to collect incoming URLLC information throughout the interval. REs used for collective referral can punch regular eMBB data which, in conjunction with other punch data, can later be transmitted.
[0055] [0055] For an implicit indication, existing eMBB control, URLLC control, DMRS and / or other signaling can be used to indicate the presence of URLLC traffic. Any of the minislot features or the eMBB slot feature (for example, eMBB pilot signals) can be used. For example, (part of) minislot and / or DMRS control can be blindly detected by EMBB UE for possible indication. If eMBB traffic is programmed in multiple aggregate slots, then, in each slot, the DMRS can signal whether or not that slot contains a low-latency transmission. For example, in each TTU / latency-tolerant transmission slot,
[0056] [0056] Figure 5 illustrates a modality for explicit post-indication of minislot traffic. In this example, a minislot duration 502 is preconfigured and / or static; an initial minislot location is also pre-configured. An indicator sequence 506 can identify time and frequency resources reserved for minislot signaling. For example, if a latency-tolerant transport block spans x number of minislot granularities in frequency and y number of minislot granularities in time, then the post-indication can contain xy number of bits to identify which time-frequency areas are submitted to preemption. If overloading is a concern, only time and / or frequency domain preemption information can be carried. According to the example above, a post-indication can contain x bits (y bits) only if the time domain (frequency) preemption information is provided. In another example, several time-frequency resources can be grouped and a group-based preemption indication can be provided, which may require fewer bits when compared to the case where information for all time-frequency resource granularities within a latency-tolerant TTU are carried.
[0057] [0057] As can be seen from the content above, there are many ways to indicate to a UE EMBB the presence of low latency transmission (eg URLLC traffic) during a latency-tolerant transmission (eg eMBB ). For example, a puncture or indication of preemption (PI) can be used. Alternatively or additionally, an indication can simply indicate whether a downlink transmission to the EMBB UE is present or not. Alternatively or additionally, an indication of whether or not a low-latency (preemptive) transmission to another UE (for example, an UE URLLC) can be used. For example, an indication that a latency-tolerant transmission to the EMBB UE is present can also be an indication that a low-latency (preemptive) transmission to another UE (for example, an EU URLLC) is not present and, conversely, an indication that a latency-tolerant transmission to the EMBB UE is not present can also be an indication that a low-latency (preemptive) transmission to another UE (e.g., URLLC UE) is present. Other possibilities exist for the indication.
[0058] [0058] Figure 6 illustrates a modality flow of a communication scheme with the use of punching or preemption indications (PIs) to indicate, to a latency-tolerant UE, the presence of second data (for example, low data for a low-latency UE in resources programmed for first data (for example, latency-tolerant data) for the latency-tolerant UE. As shown in Figure 6, a configuration indication is transmitted from a gNodeB (gNB) / eNB to a latency-tolerant UE, such as an eMBB UE in step 601. The configuration indication can contain one or more parameters to enable the UE handles IPs appropriately. For example, the configuration indication can be used to notify the eMBB UE that preemption may occur and / or to turn on or activate a monitoring function in the eMBB UE to monitor one or more POIs, which may indicate the presence of second data ( for example, low latency traffic) on resources allocated in DL programming grants to the EU eMBB. In step 602, the gNB can transmit a DL scheduling concession (for example, for the T1 programming interval) to the EMBB UE, and in step 603, the gNB can transmit first DL data (for example, data tolerant) latency) to the EMBB EU. The indication and grant, in steps 601 and 602, can be transmitted in different messages or in a message. As shown in step 604, the eMBB UE can monitor PIs during a T1 monitoring period which, in the example in Figure 6, is equal to the T1 programming interval. In other modalities, for example, when IP is a common group indication, the monitoring period can be different from a schedule interval (for example, longer or shorter) and, for example, cover multiple schedule intervals or just one portion of an interval. In some modalities, the configuration indication specifies the monitoring period. The monitoring activity can start at different points in time, for example,
[0059] [0059] In step 605, gNB can transmit a DL programming grant to a low-latency UE, such as a UE URLLC and, in step 606, gNB can transmit second DL data (for example, low data latency) to the EU URLLC. In step 607, one or multiple POIs (only one shown) can be transmitted by gNB to eMBB UE to indicate the presence of second data (for example, low latency traffic on resources identified in the DL programming concession transmitted in step
[0060] [0060] In step 608, another configuration indication is transmitted from gNodeB to eMBB UE, for example, alerting eMBB UE to turn off or disable the monitoring function for preemption indications during a period without T2 monitoring, which, in the example in Figure 6, is equal to the programming interval T2. In other examples, the period without monitoring may differ from a schedule interval (for example, greater or lesser) and, for example, cover multiple T2 schedule intervals or just a portion of a T2 interval. In some embodiments, the configuration indication, shown in step 608, may include the same set, or a different set, of configuration parameters and / or may have the same format or a different format than the configuration indication shown in step 601 In step 609, the gNB can transmit a DL scheduling grant (for example, for T2 scheduling interval) to the EMBB UE, and in step 610, the gNB can transmit third party DL data (for example, latency-tolerant data ) to the EMBB EU. The indication and grant, in steps 608 and 609, can be transmitted in different messages or in a message. Since the EMBB UE received the configuration indicator to turn off its monitoring function, the EMBB UE does not monitor, during the T2 interval, the preemption indicators, as shown in step 611.
[0061] [0061] In some embodiments, the configuration indication includes one or more parameters to enable the EMBB UE to properly handle preemptive transmissions or events that can be indicated by PIs that the eMBB receives subsequently. As will be explained in more detail below, PI includes an indication of a time and / or frequency preemption region (PR) and a bitmap of bits associated with different portions of the PR and each indicates whether a preemptive transmission is present in the corresponding portion of the PR.
[0062] [0062] Figure 7 illustrates a structure modality of a configuration indication. In some embodiments, the configuration indication is transmitted to the eMBB UE using, for example, an RRC message or other type of semi-static or higher layer signaling. In the example in Figure 7, a semi-static configuration indication includes a monitoring interval indication field, a time and / or frequency granularity indication field (for example, containing a time and / or frequency resolution for the bits in the PR bitmap (more details below), a time-frequency region indication field (ie PR), an activity duration field (for example, containing a duration when the setting is valid) and / or a temporary radio network identifier (RNTI) field. The configuration indication can additionally include a notification of the PR bitmap format for certain N payload bits. For example, N = xy bits, where x is the number of time splits / granularities and y is the number of frequency splits / granularities. The values of x and y can also be included in the configuration indication. Different values of pair {x, y} are possible which all have xy = N bits. The configuration indication can also notify the EMBB UE of how a two-dimensional PR bitmap is converted to an N bit bitmap.
[0063] [0063] In one example, the PR bitmap has N = 16 bits, which corresponds to a PR that is divided into 16 resource units and each bit represents a resource unit. In Table I, resource unit indices are shown, in which columns indicate time granularities and lines indicate frequency granularities. There are four time granularities x = 4 and four frequency y = 4 configured. Table I t1 t2 t3 t4 f1 1 2 3 4 f2 5 6 7 8 f3 9 10 11 12 f4 13 14 15 16 There are different ways in which the bits representing different resource units can be grouped into N bits. In one example, N bits are organized as [f1, f2, f3, f4], that is, [1,2,3,4,5, .., 8,9, .., 12,13, .., 16] (entries are inserted one line after another) or [t1, t2, t3, t4], that is, [1,5,9,13,2,…, 14,3, .., 15,4, …, 16] (entries are inserted one column after another). In this document, 16 bits and x = 4 and y = 4 are used as an example only. In practice, x and y can be any positive integers and a similar mapping or conversion technique can be applied to any combination of pair {x, y}. There may be other alternative ways of grouping the bits that represent the units, with different interleaving patterns, and this is notified to the UE.
[0064] [0064] The configuration indication can also notify the eMBB UE of how many or on what occasions the eMBB UE needs to monitor POIs. As mentioned above, an eMBB UE can monitor PIs in Y number of occasions in time and / or frequency. The exact value of Y can be notified, explicitly, through semi-static signaling (for example, RRC) or it can be derived, implicitly, from the transmission duration and / or from the location and number of RBs assigned for transmission of data and / or location of PDCCH monitoring occasion for granting DL in relation to PDCCH monitoring occasions for PIs.
[0065] [0065] As noted above, in one mode, it is possible that all parameters in the configuration indication are grouped and sent in a configuration indication message. Alternatively, one or more parameters can be sent in different signaling messages using semi-static or dynamic signaling (for example, DCI). Semi-static signaling options include broadcast signaling, such as MIB or SIB or EU-specific RRC signaling. Another group-based or cell-specific RRC signaling is also possible. For example, monitoring periodicity (ie, configured location range / search spaces) of a common group PI can be notified via MIB or SIB, while other parameters can be notified at different stages of RRC signaling. Alternatively, if only a select group of UEs is configured to monitor, then EU-specific or group-based RRC signaling can be used.
[0066] [0066] Referring again to Figure 7, the time and / or frequency granularity information may comprise a PR bitmap (more details below), and the time-frequency region may comprise a scope of the preemption indication . In one embodiment, the bitmap can correspond to a time-frequency region that includes or excludes reserved or unused resources. The time-frequency region, that is, the preemption region can be contiguous or non-contiguous. When a UE receives a PI associated with a downlink transmission, the UE may store the received transmission signal in temporary storage, and otherwise abandon or discard, from the temporary storage, the received signal bits or symbols that have been received through portions of the time-frequency region where preemptive downlink transmissions (e.g., URLLC transmission) are indicated as being present by the PR bitmap field. Alternatively, in modalities in which the UE receives the PI during the preemption event, the UE can store a subset of bits or symbols of the received signal in temporary storage without storing, in temporary storage, bits or symbols of the received signal that were received through portions of the time-frequency region in which preemptive downlink transmissions are indicated as being present by the PR bitmap field.
[0067] [0067] In some deployments, the use of semi-static configuration indications, as described above, may not sufficiently represent the variety and number of low-latency transmissions that may preempt latency-tolerant transmissions. For example, depending on the programming load, quality of service requirements or available resources, low latency transmissions can be programmed dynamically across many different time-frequency regions, both grouped in a particular area where, for example, a small number of eMBB UEs can be impacted or dispersed in many different regions that affect a larger number of UEs. In these situations, if the configuration of the PIs does not change quickly enough (for example, semi-static), or if the resolution provided by the PR bitmap in the PI is too thick or if the coverage provided by the PR bitmap is too large, PIs may inadvertently notify some eMBB UEs that their downlink transmissions have been subjected to preemption when, in fact, they have not been. This can be particularly true when the configuration indication and PIs serve a group of UEs and / or the number of bits used in the PR bitmap is small.
[0068] [0068] Figure 8 illustrates two preemption indications (PIs) 809, 810 of low latency traffic, in which each PI corresponds to a time-frequency region (ie, a PR) that is divided into two frequency partitions and two time partitions. In the example in Figure 8, it is assumed that the PIs have been (pre-) configured by a semi-static configuration indication. In this example, PIs 809, 810 each include a 4-bit bitmap, where each bit corresponds to a particular time-frequency portion of the PR and indicates whether preemption has occurred or not. The PI PR bitmap 809 addresses subregions 801 to 804 and the PI PI bit map 1010 addresses sub-regions 805 to 808. Each bit of the PR bitmap, in each of the PIs 809 and 810, correspond to a particular sub-region and indicate the presence or absence of URLLC data or whether the sub-region is subject to preemption or not. A first transmission of eMBB 814 occurred during the first to second time partitions, and a second transmission of eMBB 815 occurred during the third to fourth time partitions. The first and second time partitions are covered by PI 809, while the third and fourth time partitions are covered by PI 810.
[0069] [0069] As can be seen, a first data transmission of URLLC 811 occurred in the time-frequency sub-regions 801 and 804, and the first PI 809 uses 1, 0, 0 and 1 to indicate the preemption status of each one of the time-frequency sub-regions 801 to 804, respectively, using 1 to indicate the presence of URLLC data transmission and 0 to indicate the absence of URLLC data transmission. Similarly, a second and third data transmission of URLLC 812 and 813 occurred in the 805-808 time-frequency sub-regions, and the second PI 810 uses 1, 1, 1 and 1 to indicate the preemption status of each one of the time-frequency sub-regions 805-808, respectively.
[0070] [0070] While PI 810 accurately indicates the preemption status of the second transmission of eMBB 815, the granularity or resolution of PI 809 is such that it can indicate that the first transmission of eMBB 814 is impacted by the transmission of URLLC 811, but not that it is, in fact, subjected to preemption. In this way, a dynamic IP configuration with an adaptive indication of PR is beneficial to more accurately indicate preemption events.
[0071] [0071] There are many ways to dynamically and more accurately reflect the presence of different sets of low-latency transmissions in latency-tolerant transmissions. In some modalities, for each PI transmission that indicates the presence of certain low-latency transmissions, the PI includes both a bitmap of a PR that is large enough to cover the impacted time-frequency resources and an indication of PR that indicates time-frequency portions of the PR that correspond to the bits in the PR bitmap. The indicated portions can represent the whole PR or a part of a PR (a particular set of resources in it). The PR indication can include, for example, (or be indicative of) one or more of the following aspects or parameters, in any combination: 1) a PR location, 2) a time-frequency resolution (for example, granularity frequency bitmap) of the PR bitmap, 3) a type or format of the PR bitmap, and
[0072] [0072] Any of the parameters can be changed dynamically (for example, in each PI transmission) depending on the number and placement of the low latency transmissions in relation to the latency-tolerant transmissions in progress. In other modalities, any of these parameters can be configured in advance with default or initial values, for example, through a configuration indication (semi-static). With or without previous configuration, including these parameters in the PI (using one or multiple fields), the time-frequency portions indicated by the bits in the PR bitmap can be changed dynamically, to indicate , more precisely, the presence of low latency transmissions that can be programmed dynamically in different time-frequency resources. In some embodiments, the PR frequency range is less than or equal to a carrier BW and the PR duration can be equal to or less than the configured PI monitoring period (for example, through the configuration indication).
[0073] [0073] Figure 9 illustrates two low-latency traffic PIs that correspond to a first time-frequency region that is divided into two frequency partitions and two time partitions 901 to 904, and a second time-frequency region which is divided into two frequency partitions and two time partitions 905 to 908. There are eight subregions 901 to 908 and two four-bit PIs 909 to 910 where each bit corresponds to a particular subregion and indicates the presence or absence of URLLC data or whether the sub-region is subject to preemption or not. A first transmission of eMBB 914 occurred during the first to the second time partitions (and longer than the first to the second time partitions here), and a second transmission of eMBB 915 occurred during the third to the fourth time partitions. As can be seen, a first data transmission of URLLC 911 occurred in the time-frequency sub-regions 902 and 903, and the first PI 909 uses 0, 1, 1 and 0 to indicate the preemption status of each one among the time-frequency sub-regions 901 to 904, respectively. Similarly, a second and third data transmission of URLLC 912 and 913 occurred in the time-frequency sub-regions 905 to 908, and the second PI 910 uses 1, 1, 1 and 1 to indicate the preemption status of each one of the time-frequency sub-regions 905 to 908, respectively. When compared to Figure 8 or sub-regions 905 to 908, the four sub-regions 901 to 904 are adaptive to the transmission of URLLC 911, and are smaller than sub-regions 801 to 804 or sub-regions 905 to 908. PI 909 indicates the presence or absence of URLLC data with finer granularity in the time-frequency domains than PI 809 in Figure 8, and more accurately indicates the presence of URLLC 911 data transmission. PR indication or PR notification sent as part of PI 909 can adaptively configure one or more aspects of a PR (eg location, resolution, format, number of bits) that results in more accurate notification of event preemption and potentially less impacted actual eMBB transmissions.
[0074] [0074] In some embodiments, EU-specific or group-common downlink control (DCI) information can be used for PI transmissions and each PI can include a bitmap of a PR that is large enough to cover resources impacted time-frequency and a PR indication in the form of one or more fields that indicates the time-frequency portions of the PR that correspond to the bits in the PR bitmap. PR can alternatively be called a preemption indication region or coexistence region or impacted region.
[0075] [0075] In some embodiments, a DCI message is transmitted which notifies the region (that is, the preemption PR region) where preemption events occurred and the preemption information bitmap that provides preemption status in different portions Of region. The DCI message can dynamically update one or multiple IP configuration parameters, for example, location of PR, that is, start / end positions in time / frequency in relation to a reference point and / or duration PR and / or time and / or frequency granularity (ie, bitmap bit resolution) of PI and / or number of partitions in time and / or frequency within the PR (ie bitmap format) x by y, x and / or y values). Examples of reference points mentioned above include CORESET time-frequency location of PI monitoring occasion, NR carrier center / boundary, channel number used for channel raster and / or synchronization, or RMSI BW center / boundary ,
[0076] [0076] Figure 10 illustrates a modality of construction of common group DCI for a preemption indication (PI) 1000. Group DCI or common group DCI (GC DCI) for preemption indication can comprise field A with a notification PR 1002, field B with a bitmap that provides preemption information within PR 1004, field C with a bitmap configuration and / or PR 1006 and / or other additional fields 1008. The group DCIs for indicating preemption can adaptively indicate a PR based on the area (s) where actual preemption events occur. In this way, more accurate preemption information can be provided based on the actual location of preemption events when compared to the preconfigured area, thus resulting in better eMBB UE performance and higher throughput. In one embodiment, group DCIs for indicating preemption may be a post-indication, that is, the indication addresses preemption events that occurred prior to the occasion of IP monitoring. Alternatively, group DCIs can be sent during the preemption event and the PI can adaptively indicate the PR and / or PR bitmap based on the current preemption event. The construction of group DCI for PI may be subject to payload restrictions of group DCI or how many payload formats or sizes are supported.
[0077] [0077] In a first example, time and / or frequency granularity format, that is, bitmap x by y can be pre-configured, in which values of x and y are configured in a semi-static way. The resolution can be configured semi-static or dynamically updated as part of PI. For example, an N2-bit payload is used in a bitmap to indicate impacted portions within a PR. The bitmap can correspond to the indicated PR. For a fixed payload size bitmap,
[0078] [0078] In a second example, the number of time and / or frequency partitions within PR (ie x and y values) and granularities (ie resolution or area of a resource unit represented by each map bit) bits) can be adaptive. For example, N1 bits can be used for the PR field notification, and N2 bits for the bitmap field. Various configurations or formats of a bitmap can be notified in a semi-static manner and a configuration can be notified dynamically as part of PI. For example, when N2 = 16 bits, a setting of field B 1004 can be 8 by 2, and another setting of field B 1004 can be 4 by 4. Field C 1006 can indicate which option is used for the current PI. In this example, the individual bit numbers in fields A 1002 and B 1004 do not change. As shown in Table II, 8 bits are used in field A 1002 for PR notification and 12 bits are used in field B 1004 for bitmap. The bitmap configuration can be any of 4 by 3, 3 by 4, 6 by 2, 2 by 6, or some other configuration. Several configurations can be notified to the UE for a given bitmap payload, such as N2, the number of bits in field B. A configuration can be indicated in field C to be used for the current PI being used. For the example below in Table II, Field C has 2 bits to differentiate four configurations from bitmaps, and each C index number corresponds to one of the four configurations. Table II A (# bits) B (# bits) C (configuration index) 8 12 (4 by 3) 1 8 12 (3 by 4) 2 8 12 (6 by 2) 3 8 12 (2 by 6) 4
[0079] [0079] Alternatively, the numbers of bits in fields A and B can be variable while keeping the sum N of N1 and N2 fixed. In this way, a more dynamic scenario of flexible PR and bitmap indication is supported. For example, more bits for PR suggest fewer bits for bitmaps, and vice versa. A given value of N2 bits can suggest a configured bitmap, or several candidates for a given value of N2 bits can be configured and a specific configured bitmap can be indicated in the PI. The C 1006 field can indicate the configuration used for the current PI. As shown in Table III, a total of 20 bits is used in field A 1002 and field B 1004 for notification of PR and bitmap fields, respectively. A number of configurations can be supported for a given value of N2 bits, for example, the configuration of the bitmap can be any one of 4 by 4, 8 by 2 for N2 = 16, 4 by 3, 3 by 4, 6 by 2, 2 by 6 for N2 = 12, 5 by 2 for N2 = 10, 4 by 2 for N2 = 8, or some other configuration. Fields A and B can be configured and adapted dynamically. The index indicated in field C notifies a given combination of N1 and N2 bits and a corresponding configuration for PI. In this example, field C has 3 bits, so field C can indicate up to 8 combinations, index 1 in field C indicates that the number of bits in field A is 4, the number of bits in field B is 16 , and the bitmap setting is 4 per
[0080] [0080] Resolutions can also be displayed dynamically, and this can result in an increased number of bits used in field C. As shown in Tables IV and V, for the same configuration as a bitmap, different resolutions can be indicated by field C
[0081] [0081] Figure 11 illustrates a modality of adaptive notification of a RP. The notification of PR in group DCI Field A may comprise indication of time-frequency region indicating the starting position and / or the ending position and / or any other reference position (eg center) of / within the width bandwidth (BW) of the PR in the frequency domain, and / or a size or frequency range (for example, RBGs / subband) in the frequency domain. In addition, the PR notification in Field A of group DCIs may include indication of the time-frequency region that indicates the start position and / or the end position and / or any other reference position (for example, center) of / within the PR duration, and / or the duration (for example, in slots / symbols / ms) in time domain. The location of PR in time and / or frequency can be indicated in relation to a reference point. For the two time durations 1102 and 1104 of PRs, the bitmap setting is displayed dynamically. The initial positions in time and frequencies and resolutions of the bitmaps are different while the N2 number of bits used for the bitmaps in both cases is the same --16. As can be seen in Figure 11, the areas of the two PRs indicated by the adaptive PR notification are different, and the granularities of time-frequency regions of the two PRs that correspond to each bit among the 16 bits are also different.
[0082] [0082] The construction of N1 bits in Field A of group DCI can comprise different configurations. For example, the frequency location (for example, start position) and frequency range can be provided, and the N1 bits can be used to indicate the start position and / or duration of time. Or, the initial position of time and duration can be provided, and the N1 bits can be used to indicate location (for example, starting position) and / or frequency range. Alternatively, the N1 bits can be further divided into N1f and N1t bits, and the N1f and N1t bits indicate the starting position in frequency and time, respectively. The higher layer signaling can notify a UE of which configuration in Field A is used, that is, what is the value of N1f and N1t for a given value of N1. N1 bits can be constructed as [N1f bits N1t bits] or [N1t bits N1f bits], that is, time indication can be followed by frequency indication or vice versa. For certain N1 bits, one of several candidate configurations can be indicated using the C field in the group DCI. For example, N1 = 4 bits can be divided into N1f = 2 and N1t = 2 or N1f = 1 and N1t = 3, etc., and one of the configurations for a given N1 payload is indicated in PI, for example, by middle of field C.
[0083] [0083] Not all components of the notification can be indicated dynamically. In a first example, the starting position in time and / or frequency is dynamically notified while the frequency size and / or time duration is indicated in a semi-static way or obtained from the PI bitmap configuration, as as a chosen bitmap configuration. Each bit can correspond to a unit of time-frequency resource for a given bitmap configuration, for example, the resolution of a bit is known to the UE. If there are four frequency divisions configured or reported in a semi-static manner, then the frequency range can be obtained as four times the size of each time-frequency unit in frequency. In a similar way, the duration of time can be obtained.
[0084] [0084] In a second example, the starting position in frequency and / or duration of time is reported in a semi-static manner while the frequency range and / or duration of time is dynamically indicated to the UE. The indication for the frequency range and / or length of time can be implicit or explicit. The frequency range or time duration can be obtained dynamically based on explicit signaling, such as bitmap indicated for preemption events and their configuration and / or resolution. For example, the frequency range or length of time covered by each bit can also be displayed dynamically.
[0085] [0085] In a third example, both the initial position in time and / or frequency and the size of frequency and / or duration of time are dynamically indicated. The frequency range or time duration can be obtained dynamically based on explicit signaling, such as the end position or duration or time / frequency range is indicated in addition to the starting position or bitmap indicated for preemption events and their configuration and / or resolution. For example, the frequency range or length of time covered by each bit can also be displayed dynamically. The indication for frequency range or time duration can be implicit or explicit. If start and end positions are indicated for a PR, no separate bit resolution notification, in the indicated bitmap, can be sent. In this case, the resolution can be obtained by dividing the range / duration by the indicated number of time / frequency divisions / partitions in the bitmap, that is, x and y values.
[0086] [0086] The initial position in time / frequency can be indicated based on a granularity of i RBGs in frequency and j symbols / slots / ms in time, in relation to a given numerology. Some candidate positions, such as M frequency locations and / or N time locations within a potential scope of PI can be configured semi-static, and Log2M and / or Log2N bits can be used to indicate the starting position in time and / or frequency between configured locations. The configured locations can be defined or obtained as a detour or offset from a reference point. Therefore, there may be M possible deviations in frequency and / or N possible deviations in time from a reference point within a potential scope of PI that can be configured in a semi-static manner.
[0087] [0087] A frequency range and time duration can be contiguous or non-contiguous. When the frequency range or time duration is contiguous, possible range / duration values (L) can be configured by a higher layer, and one of them can be indicated, such as by Log 2L bits. When the frequency range or length of time can be non-contiguous, and if dynamic, a bitmap to notify PR can be used. If the unused area is configured semi-static, the bitmap indication for PR may not be necessary and the range / duration indication may be sufficient. The UE, based on semi-static notification of unused / reserved / unknown resources, identifies the effective region within the PR, that is, even if an unused resource is included in the scope of the PR, the UE can assume that the map of PI bits only correspond to the area that can, in fact, be subjected to preemption. In some cases, a single PI can correspond to disjunct frequency bands.
[0088] [0088] Figure 12 illustrates a non-contiguous PR modality. The indicated PR can be non-contiguous in time and / or frequency, for example, with programming of part of cross-bandwidth within a carrier. A set of UEs can be programmed using non-contiguous BWP1 1202 and BWP2 1204. Bandwidth 1206 with numerology k between BWP1 1202 and BWP2 1204 can be unknown by a UE or reserved. BWP1 1202 and BWP2 1204 have numerologies i and j, respectively, and numerologies i, j and k can be the same or different. In this example, the search space for PI can be in BWP 1 or BWP 2. The PI bitmap corresponds to parts of PR in BWP 1 and 2. In one embodiment, f1 and f2 can correspond to the part of PR in BWP 1 and f3 and f4 can correspond to BWP 2 in Table I.
[0089] [0089] Although the illustrations are shown for common group PI, the same modalities can also be applied for EU specific PI. For example, pre-configured / standard PR for a UE is the time-frequency resources allocated in the DL grant and the UE can receive a PI after being programmed in which the PI can dynamically update the PR based on actual location of preemption events that overlap with the allocated resources of the UE.
[0090] [0090] Figure 13 illustrates a common group DCI structure modality (GC DCI). Several types / formats can be configured by a higher layer, and one can be dynamically indicated in GC DCI. As shown in Figure 13, DCI GCs can comprise a type field, a payload field and / or a temporary radio network identifier (RNTI) field. GC DCI content can be configurable. The same DCIs can be used to provide one or multiple types of control information. For example, if GC DCIs are for PI only, a first type of payload has a common field (s) read by all UEs. The common field (s) provide bitmap of preemption information for a configured region, or both region and bitmap of preemption information are transported together in a dynamic manner. A second type of payload can comprise a number of specific UE fields in GC DCIs, and the payload can be divided into N specific UE fields. Each of the N specific UE fields can be configurable according to parameters or transmission properties of a UE (for example, transmission duration, TB size, BW part size, RBs assigned in the DL grant, etc.) . A third type of payload can be a combination of the first and second types, that is, the payload is divided into two portions. The first portion contains common information field (s) for a first group of UEs while the second portion is divided into specific EU fields for a second group of UEs.
[0091] [0091] Alternatively, GC DCIs can combine multiple types of control information instead of just for PI. A first type of payload under this category can provide PI only, a second type of payload can provide PI and other types of control information, and a third type of payload can provide one or more other types of control information.
[0092] [0092] Group DCIs may have specific UE fields to adjust the content of each field according to the parameters of each UE transmission. For example, a first UE may require increased coverage and is programmed with a longer interval while a second UE may be programmed with a shorter duration with or without occupying large frequency resources. According to another example, retransmission sometimes takes a shorter duration than the initial transmission. Thus, a single-size granularity of PI may not be beneficial to all UEs and, consequently, the performance of UEs may be affected with a PI with single-size granularity.
[0093] [0093] When the payload size of the group DCI is fixed, the payload construction can be configurable. For example, the payload may not be EU-specific, but it may be common to a group of UEs that monitors for preemption indications. Alternatively, the payload is divided into specific UE fields, and each specific UE field can be further configured. For example, each UE field can have N bits while time granularity and / or configured frequency can be the same or different for different UEs. The dynamic indication of bitmap and / or PR configuration and / or bit granularity / resolution in the bitmap can be adapted independently for each UE. Or, a specific UE field may differ in the number of bits from another specific UE field. In some cases, some IP content may be common while some content may be UE specific. For example, the bitmap configuration may be common to UEs, however, bitmap and / or PR information may be different.
[0094] [0094] The payload size may vary or can be configurable. Different formats can be supported. UEs can be notified by DCI, by a system information block (SIB), by RRC, or by media access control element (MAC CE) of (re) configured payload size and GC DCI configuration, and with what type of GC DCI UEs are configured to monitor or decode. The payload can be divided into a specific EU field and / or common field.
[0095] [0095] As discussed above, the payload size can be fixed or configurable, and GC DCI can provide one or multiple types of such information. DCI GCs can provide preemption information only or other common information in addition to preemption information. The payload content can be configurable, for example, sometimes GC DCIs carry only PI, other times, GC DCIs provide other types of information, or both. UEs can be preconfigured considering the structure and configuration of GC DCI and / or which configuration is active for a period of time. DCIs (EU / group-based) can also activate a certain group DCI setting.
[0096] [0096] The research space of GC DCIs that carry IP may or may not be shared with other EU-specific DCIs or GC or PDCCH. In some cases, GC DCI for PI may be transmitted in a specific EU research space. For example, when UE BWP has no common search space configured in it, and no UE-specific PDCCH to receive, then eNB can use UE-specific search space to send GC DCI to PI. This can be applicable to any type of GC DCI.
[0097] [0097] Multiple DCI formats can be used to send POIs. The UE can be notified of semi-static PI configuration and a DCI format can update the configuration. For example, DCI 1 format can be used to send bitmap preemption information to a pre-configured PR. The DCI 2 format can be used for adaptive PR notification in conjunction with the bitmap. When the DCI 2 format is received, it can override the default PR configuration and / or bitmap configuration. The DCI 1 and 2 formats can have the same or different payload. The DCI 1 and / or 2 format can also include other types of control information. A UE can be configured to support both or one of the same or none.
[0098] [0098] The preemption (PR) or coexistence region is defined as a time-frequency region in which eMBB transmissions can be subjected to preemption due to overlapping URLLC transmissions. GC DCI in PDCCH indication can contain N bits to carry preemption information to a PR. Different GC DCIs in PDCCHs can correspond to different PRs. Multiple GC DCIs in PDCCHs can be sent at the same time or at different times that correspond to overlapping or non-overlapping PRs. An eMBB UE can monitor one or multiple GC DCIs in PDCCHs depending on how the UE transmission overlaps parts of the PR (s). Multiple PRs can be contiguous or non-contiguous in frequency and / or time.
[0099] [0099] At any given time, there may be one or multiple PRs activated. A UE transmission can be contained within a PR or span multiple PRs, and PRs can be of the same or different numerologies. Alternatively, a particular PR can be segmented into multiple parts in time and / or frequency, and a GC PI can be sent to each part. The configuration of a PR can be notified by means of UE-specific or cell-specific signaling by either RRC or DCI.
[0100] [0100] A PR can be enabled or disabled by DCI, such as EU-specific DCI or GC DCI. Alternatively, receiving RRC configuration can suggest an activated PR. The IP numerology can be the same or different from the numerology used in PR (s). Multiple numerologies can coexist within a PR, for example, in frequency division multiplexing (FDM) and / or time division multiplexing (TDM) mode. The granularity of time and / or frequency of a PI can be according to a specific numerology.
[0101] [0101] Figure 14 illustrates another modality of adaptive notification structure for a PR. As shown in Figure 14, each GC DCI A 1410, 1412, 1414 corresponds to a PRA 1402, 1404, 1406, respectively, and GC DCI B 1416 corresponds to a PRB 1408. A GC DCI payload can be fixed, for example , N bits, and the size of a PR in time and / or frequency can be configured with different values. As can be seen, the size of PRA 1402 is different from the size of PRA 1406, the size of PRA 1402 or 1404 is equal to the size of PRB 1408, and the granularity of divisions in the PRA 1402 time-frequency region is different from the granularity of divisions in the PRB 1408 time-frequency region. In other words, the area of a PR (for example, PRA) and the granularity of notification of preemption information in a PI to a PR can be updated or (re) configured. A UE can be notified of reconfiguration of a PR by signaling RRC or DCI. GC DCI for PI to PRA can be monitored after a TA, PR duration, and TA, PR can be notified to the UE through RRC signaling. The TA, PR duration can be configured with different values.
[0102] [0102] GC DCI for PI can be monitored inside or outside the corresponding PR, for example, the search space for GC DCI for PI may or may not be configured within the PR. UEs that are monitoring GC DCI can be notified of their research space in a semi-static manner, for example, by means of RRC signaling. In this example, each 9-bit GC DCI bit A 1410, 1412, 1414 corresponds to a block in a 3 by 3 resource grid of PRA 1402, 1404, 1406 and indicates a configurable resource unit,
[0103] [0103] Figure 15 illustrates a modality of UE behavior when monitoring GC DCI with common preemption information. As shown in Figure 15, each UE can be notified of an IP monitoring periodicity sent in the form of GC-DCI on a PDCCH in a control resource set (CORESET). The notification of the periodicity to monitor the PI in a CORESET can be carried by means of RRC signaling, such as EU-specific or group-specific (eg cell-specific) RRC signaling or system information.
[0104] [0104] The common group indication in a CORESET can be configured to be received at each K slots / symbols for a given numerology. The K value can be configurable and different for each numerology. For example, if the common group PDCCH is sent to each K slots / symbols, it may contain indication related to the areas preempted / impacted by transmissions through a group of symbols / slots that appeared at or before the location it contains the indication.
[0105] [0105] In one example, a monitoring interval of X ms can be configured to monitor PI, where X ms is common across all numerologies. X ms can consist of L> = 1 slots for f0 = 3.75 kHz and 2N * L slots for f = 2N * f0 kHz for the same or different overload / type of CP. Alternatively, X ms can consist of L> = 1 symbols for f0 = 3.75 kHz and 2N * L slots for f = 2 N * f0 kHz for the same overload / type of CP. Therefore, the monitoring interval in # slots / symbols can be scalable through numerologies. For a given TBS, eMBB transmission can use a 15 kHz slot while it can comprise slots aggregated in larger subcarrier spacing. A common monitoring interval
[0106] [0106] In another example, the same or different monitoring frequency in slots / symbols can be configured for different types of CP for a given numerology.
[0107] [0107] In another example, the granularity of time and / or frequency of indication of preemption can be scalable through numerologies. For example, if L symbols are configured as time granularity for f0 for a given type of CP, then 2N * L symbols can be time granularity for 2 N * f0 subcarrier spacing. The similar scalable relationship in terms of RBGs or Hz is also possible in the frequency domain.
[0108] [0108] After a UE is programmed, the UE can start monitoring the GC-PDCCH from the next occasion, for example, the UE1 starts monitoring the next PI transmitted on a GC-PDCCH 1504 after being programmed. After the UE is programmed, the UE can ignore x monitoring occasions, for example, UE 2 ignores an IP or GC-PDCCH 1504 monitoring occasion and starts monitoring GC-PDCCH from the PI or GC-PDCCH 1506. The UE may ignore a monitoring occasion if it is within the symbol / us of receiving a DL grant. Within the y symbol, there may be no preemption, since an eNB can prevent preemption by programming eMBB and URLLC transmissions in resources not overlapping for that duration.
[0109] [0109] An UE can ignore monitoring for a period of time, for example, UE 2 ignores monitoring of GC-PDCCHs 1510 and
[0110] [0110] The monitoring periodicity of an EU-specific PDCCH in a CORESET and GC-DCI in PDCCH in a CORESET can be the same or different. Whether the monitoring periodicity of an UE-PDCCH and GC-DCI in PDCCH is the same or different may or may not depend on whether the content of a preemption indicator has specific UE fields.
[0111] [0111] The frequency of an EU-PDCCH can be greater than the frequency of GC-DCI in PDCCH when the monitoring frequency of GC-DCI in PDCCH is in a group of URLLC granularities (for example, symbol level) or less than the duration of the configured or indicated programming interval for eMBB UEs. The periodicity of an UE-PDCCH can be less than or equal to the periodicity of GC-DCI in PDCCH when the GC-DCI in PDCCH duration is in one or a group of slot boundaries. In this way, the monitoring occasions of UE-PDCCH and GC-PDCCH may or may not align, and a data transmission duration may cover multiple monitoring occasions of UE-PDCCH and / or GC-PDCCH.
[0112] [0112] A group of UEs can be formed depending on a set of CORESET monitoring periodicity. For example, a first PI is configured for a group of UEs with a shorter monitoring period for UE PDCCH and a second PI is configured for a group of UEs with a longer monitoring period for UE PDCCH.
[0113] [0113] Figure 16 illustrates another modality of UE behavior when monitoring GC DCI with common preemption information. As shown in Figure 16, when the capacity of UE BW, such as UE 2 BWP
[0114] [0114] However, UE4 can monitor GC DCIs for PI in a different BWP, UE4 BWP2 1622, from BWP 1630 that observed a 1628 preemption transmission event.
[0115] [0115] A UE can be configured with multiple BWPs, and not all BWPs can contain the common search space. A UE can readjust / switch to the BWP that contains the common search space with a pre-configured periodicity. For example, when a GC DCI to PI monitoring / periodicity interval is 5 TTIs, the UE can switch to the BWP that contains the GC DCI for PI I every 5 TTIs.
[0116] [0116] The UE can be configured with a standard for switching BWP, for example, the UE uses a first BWP for a first duration and then switches to a second BWP for a second duration. The second BWP can have common search space and PI is monitored in the second BWP. However, both BWP1 and BWP2 can be subjected to preemption. The switching / resetting time may be a third duration which may be a function of UE capacity and the UE may not receive any transmission during switching time.
[0117] [0117] A UE can be configured with one or multiple parts of bandwidth. The DL and UL bandwidth parts are configured separately. If the UE is receiving or transmitting transmissions that have a high reliability requirement, the UE can be configured with a time pattern or hop pattern to switch from one part of bandwidth to another for transmissions from a transport block. For example, in DL communication, the UE can be programmed (dynamic or semi-persistent) with K repetitions for a TB. The repetitions can be done in different parts of the bandwidth so that the frequency diversity can be achieved when the UE combines different transmissions / repetitions of a TB. In another example, for DL communication, eNB can send subsequent TB transmissions after an initial transmission in different parts of the bandwidth. The UE can switch to a different bandwidth part during successive PDCCH / CORESET monitoring and this can be achieved by a switching pattern which can be a function of the CORESET / PDCCH monitoring interval and the pattern can be indicated accordingly. semi-static or dynamic mode to the UE. In one embodiment, a UE is configured with three parts of DL B1, B2, B3 bandwidth. If a single piece of bandwidth is active in an instant of time, a time pattern can be indicated so that B1, B2, B3 are active over non-overlapping durations t1, t2, t3, respectively. Different sequences of bandwidth activation are possible, such as B1 → B2 → B3 → B1 → B2 → B3 etc. When the UE is in Bi, i = {1,2,3}, the UE monitors CORESET in Bi.
[0118] [0118] Similarly for UL communication, for transmissions with or without concession, a UE can be configured to switch / jump from one portion of bandwidth to another for subsequent transmissions from a TB. The configuration of UL bandwidth parts and / or hop pattern can be indicated in a semi-static or dynamic way to the UE. Similar to the above modality, a UE is configured with three parts of UL B1, B2, B3 bandwidth. If a single piece of bandwidth is active in an instant of time, a time pattern can be indicated so that B1, B2, B3 are active over non-overlapping durations t1, t2, t3, respectively. Different sequences of bandwidth activation are possible, such as B1 → B2 → B3 → B1 → B2 → B3 etc. In one example, t1 = t2 = t3 is the duration of each transmission. If a UE is configured with K repetitions for a UL broadcast without concession, the UE can be configured to switch parts of bandwidth for subsequent repetitions. If the UE has a packet that arrived when B2 is active, the UE can transmit on that part of the bandwidth and then switch to B3 for the next TB repeat for the sequence mentioned above.
[0119] [0119] In some embodiments, the UL bandwidth portion configurations of a UE that is transmitting without concession may also include transmission parameters for UL transmission without concession, such as TBS / MCS, RS, control parameters of power, number of repetitions, number of supported HARQ processes etc. The activation of different BWPs can indicate different parameters configured for UL transmission without concession. Activation of BWP (s) and / or a hop pattern can be obtained by GC DCI or EU-specific or RRC configuration can suggest activation.
[0120] [0120] A portion of bandwidth configured for a UE can be used to transmit / receive through multiple numerologies simultaneously, different numerologies at different times.
[0121] [0121] Figure 17 illustrates a block diagram of a 1700 processing system modality for carrying out the methods described in this document, which can be installed on a host device. As shown, the processing system 1700 includes a processor 1704, memory 1706 and interfaces 1710 to 1714, which can (or may not) be arranged as shown in Figure 17. Processor 1704 can be any component or collection of components adapted to perform computations and / or other processing-related tasks, and 1706 memory can be any component or collection of components adapted to store programming and / or instructions for execution via the 1704 processor. In one embodiment, 1706 memory includes readable media by non-transitory computer. The interfaces 1710, 1712, 1714 can be any component or collection of components that allows the 1700 processing system to communicate with other devices / components and / or with a user. For example, one or more of the interfaces 1710, 1712, 1714 can be adapted to communicate data, control or management messages from the 1704 processor to applications installed on the host device and / or a remote device. As another example, one or more of the interfaces 1710, 1712, 1714 can be adapted to allow a user or user device (eg personal computer (PC), etc.) to interact / communicate with the processing system
[0122] [0122] In some embodiments, the 1700 processing system is included in a network device that is accessing a telecommunications network or, otherwise, that is part of it. In one example, the 1700 processing system is on a network side device on a wired or wireless telecommunications network, such as a base station, a relay station, a programmer, a controller, a gateway, a router , an application server or any other device on the telecommunications network. In other embodiments, the 1700 processing system is on a user-side device that accesses a wired or wireless telecommunications network, such as a mobile station, user equipment (UE), a personal computer (PC), a tablet-type computer, a communications device that can be used close to the body (for example, a smart watch, etc.), or any other device adapted to access a telecommunications network.
[0123] [0123] In some modalities, one or more of the interfaces 1710, 1712, 1714 connect the processing system 1700 to a transceiver adapted to transmit and receive signaling through the telecommunications network. Figure 18 illustrates a block diagram of a transceiver 1800 adapted to transmit and receive signaling over a telecommunications network. The 1800 transceiver can be installed on a host device. As shown, transceiver 1800 comprises a network side interface 1802, a coupler 1804, a transmitter 1806, a receiver 1808, a signal processor 1810 and a device side interface 1812. The network side interface 1802 can include any component or collection of components adapted to transmit or receive signaling through a wired or wireless telecommunications network. The 1804 coupler can include any component or collection of components adapted to facilitate bidirectional communication via the 1802 network side interface. The 1806 transmitter can include any component or collection of components (for example, upconverter, power amplifier, etc.). ) adapted to convert a baseband signal into a modulated carrier signal suitable for transmission via the network side interface 1802. The receiver 1808 can include any component or collection of components (eg, down converter, bass amplifier) noise, etc.) adapted to convert a carrier signal received via the network side interface 1802 into a baseband signal. The 1810 signal processor may include any component or collection of components adapted to convert a baseband signal into a data signal suitable for communication via the device side interface (or interfaces) 1812, or vice versa. The 1812 device side interface (or interfaces) can include any component or collection of components adapted to communicate data signals between the 1810 signal processor and components within the host device (for example, the 1700 processing system, area network local (LAN) ports, etc.).
[0124] [0124] Transceiver 1800 can transmit and receive signaling through any type of communication medium. In some embodiments, the 1800 transceiver transmits and receives signaling via wireless media. For example, transceiver 1800 may be a wireless transceiver adapted to communicate in accordance with a wireless telecommunications protocol, such as a cellular protocol (eg, long-term evolution (LTE), etc.), a protocol wireless local area network (WLAN) (for example, Wi-Fi, etc.) or any other type of wireless protocol (for example, Bluetooth, short-distance communication (NFC), etc.). In such embodiments, the network side interface 1802 comprises one or more antenna / radiation elements. For example, the 1802 network side interface can include a single antenna, multiple separate antennas or a multiple antenna array configured for multiple layer communication, for example, single input multiple outputs (SIMO), multiple inputs single output (MISO) , multiple inputs multiple outputs (MIMO), etc. In other modalities, the 1800 transceiver transmits and receives signaling through wired media, for example, twisted pair cable, coaxial cable, optical fiber, etc. Specific processing systems and / or transceivers may use all components shown, or only a subset of the components, and levels of integration may vary from device to device.
[0125] [0125] It should be noted that one or more steps of the modality methods, provided in this document, can be performed by corresponding units or modules. For example, a signal can be transmitted by a transmission unit or a transmission module. A signal can be received by a receiving unit or a receiving module. A signal can be processed by a processing unit or a processing module. The respective units / modules can be hardware, software or a combination of them. For example, one or more of the units / modules can be an integrated circuit, such as field programmable door arrangements (FPGAs) or application-specific integrated circuits (ASICs).
[0126] [0126] Figure 19 is a flow chart of a 1900 method modality for wireless communications, as can be performed by an UE. In operation 1902, the UE can receive, from a base station, a first signal through first resources. The first resources can be assigned to carry downlink transmissions. In operation 1904, the UE can receive, from the base station, a first downlink control indication (DCI) message. The first DCI message may comprise a bitmap that includes bits associated with different portions of a time-frequency region. Each of the bits in the bitmap can indicate whether a downlink transmission to the UE is present in the corresponding portion of the time-frequency region. Each of the bits in the bitmap can additionally or alternatively indicate whether a preemptive downlink transmission to another UE is present in the corresponding portion of the time-frequency region. The bits in the bitmap can comprise a sequence of time-division bit groups that correspond to different time-divisions. Each of the time-dividing bit groups can include one or more bits. The one or more bits in each of the time division bit groups may correspond to one or more frequency divisions, and the one or more bits in each of the time division bit groups may correspond to correspond to the same time division.
[0127] [0127] In one embodiment, the bits included in the bitmap can be consecutive bits, and each of the time division bit groups can include two or more consecutive bits. The word “consecutive” means to follow one another in succession or uninterrupted order (that is, without intervening data). In this document, the consecutive bits in the bitmap mean that the bits in the bitmap follow each other in uninterrupted succession. So, there is no intervening data between two consecutive bits in the bitmap. In addition, two or more consecutive bits in a time division group mean that bits, in the same time division group, follow each other in uninterrupted succession. So, there is no intervening data between two consecutive bits in the same time division.
[0128] [0128] In one embodiment, each of the time division bit groups can comprise a first bit and a second bit. The first bit can correspond to the same first frequency division, and the second bit can correspond to the same last frequency division.
[0129] [0129] In one embodiment, before the UE receives the first DCI message, the UE can receive a first radio resource control (RRC) message from the base station. The first RRC message can indicate a payload size of the DCI message. The first RRC message can also indicate the time-frequency region and granularities of the respective time and frequency divisions.
[0130] [0130] Figure 20 is a flow chart of a method method 2000 for wireless communications, as can be performed by a base station (BS). In operation 2002, BS can transmit a first signal to a UE through first resources. The first resources can be assigned to carry downlink transmissions. In operation 2004, BS can transmit a first downlink control indication (DCI) message. The first DCI message may comprise a bitmap that includes bits associated with different portions of a time-frequency region. Each of the bits in the bitmap can indicate whether a downlink transmission to the UE is present in the corresponding portion of the time-frequency region. Each of the bits in the bitmap can additionally or alternatively indicate whether a preemptive downlink transmission to another UE is present in the corresponding portion of the time-frequency region. The bits in the bitmap can comprise a sequence of time-division bit groups that correspond to different time-divisions. Each of the time-dividing bit groups can include one or more bits. The one or more bits in each of the time division bit groups may correspond to one or more frequency divisions, and the one or more bits in each of the time division bit groups may correspond to correspond to the same time division.
[0131] [0131] In one embodiment, the bits included in the bitmap can be consecutive bits, and each of the time division bit groups can include two or more consecutive bits. The word “consecutive” means to follow one another in succession or uninterrupted order (that is, without intervening data). In this document, the consecutive bits in the bitmap mean that the bits in the bitmap follow each other in uninterrupted succession. So, there is no intervening data between two consecutive bits in the bitmap. In addition, two or more consecutive bits in a time division group mean that bits, in the same time division group, follow each other in uninterrupted succession. So, there is no intervening data between two consecutive bits in the same time division.
[0132] [0132] In one embodiment, each of the time division bit groups can comprise a first bit and a second bit. The first bit can correspond to the same first frequency division, and the second bit can correspond to the same last frequency division.
[0133] [0133] In one embodiment, before BS transmits the first DCI message to the UE, BS can transmit a first radio resource control (RRC) message to the UE. The first RRC message can indicate a payload size of the DCI message. The first RRC message can also indicate the time-frequency region and the granularities of the respective time and frequency divisions.
[0134] [0134] The modalities in this disclosure provide technical solutions to technical problems. Low-latency data can be intermittent or sporadic in nature, and can be transmitted in small packets. So, it can be inefficient to devote resources to low latency data in conventional systems. Defining a coexistence region where resource allocation for latency-tolerant traffic overlaps resource allocation for low-latency traffic in time and frequency domains improves network functionality. Specifically, the use of a bitmap to indicate whether preemptive downlink transmissions are present in the coexistence region provides a flexible technique for efficient use of network resources through conventional systems.
[0135] [0135] Example 1. A method for wireless communications, which comprises: receiving, by means of user equipment (UE) from a base station (BS), a first signal through the first resources assigned to bear link transmissions downward; and receiving, through the UE of the BS, a first downlink control indication (DCI) message, the first DCI message comprising a bitmap that includes bits associated with different portions of a time-frequency region , and each of the bits in the bitmap indicates whether a downlink transmission to the UE is present in the corresponding portion of the time-frequency region, where the bits in the bitmap comprise a sequence of groups of time-dividing bits that correspond to different time-divisions, each of the time-dividing bit groups includes one or more bits, the one or more bits, in each of the time-dividing bit groups, they correspond to one or more frequency divisions, and the one or more bits, in each of the groups of time division bits, correspond to the same time division.
[0136] [0136] Example 2. The method, according to Example 1, in which the bits included in the bitmap are consecutive bits, and each of the time division bit groups includes two or more consecutive bits.
[0137] [0137] Example 3. The method, according to any of the previous Examples, in which each of the time division bit groups comprises a first bit and a second bit, the first bit corresponds to a first frequency division , and the second bit corresponds to a last frequency division.
[0138] [0138] Example 4. Method, according to Example 3, in which the first bit, in each of the time division bit groups, corresponds to the same first frequency division, and the second bit, in each one of the time division bit groups, corresponds to the same last frequency division.
[0139] [0139] Example 5. The method, according to any of the previous Examples, which further comprises: receiving, through the BS UE, a first radio resource control (RRC) message indicating a load size useful DCI message.
[0140] [0140] Example 6. The method, according to Example 5, the first RRC message additionally indicates the time-frequency region.
[0141] [0141] Example 7. The method, according to Example 5, the first RRC message additionally indicates granularities of the respective time and frequency divisions.
[0142] [0142] Example 8. The method, according to any of the previous Examples, in which each of the bits in the bitmap, indicates whether a preemptive downlink transmission to another UE is present in the corresponding portion of the region of time-frequency.
[0143] [0143] Example 9. A user equipment (UE) configured for wireless communications, the UE comprises: a non-transitory memory storage comprising instructions; and one or more processors in communication with the memory, in which the one or more processors execute the instructions to: receive, from a base station (BS), a first signal through the first resources assigned to bear downlink transmissions; and receive, from BS, a first downlink control indication (DCI) message, the first DCI message comprises a bitmap that includes bits associated with different portions of a time-frequency region, and each one among bits, in the bitmap, indicate whether a downlink transmission to the UE is present in the corresponding portion of the time-frequency region, where the bits in the bitmap comprise a sequence of time-splitting bit groups which corresponds to different time divisions, each of the time division bit groups includes one or more bits, the one or more bits, in each of the time division bit groups, correspond to one or more divisions frequency, and the one or more bits, in each of the time division bit groups, correspond to the same time division.
[0144] [0144] Example 10. The UE, according to Example 9, in which the bits included in the bitmap are consecutive bits, and each of the time division bit groups includes two or more consecutive bits.
[0145] [0145] Example 11. The UE, according to any of the previous Examples, in which each of the time division bit groups comprises a first bit and a second bit, the first bit corresponds to a first frequency division , and the second bit corresponds to a last frequency division.
[0146] [0146] Example 12. The UE, according to Example 11, the first bit in each of the groups of time division bits corresponds to the same first frequency division, and the second bit in each of the groups time division bits correspond to the same last frequency division.
[0147] [0147] Example 13. The UE, according to any of the previous Examples, in which the one or more processors additionally execute the instructions to: receive a first radio resource control (RRC) message that indicates a size payload of the DCI message.
[0148] [0148] Example 14. The UE, according to Example 13, the first RRC message additionally indicates the time-frequency region.
[0149] [0149] Example 15. The UE, according to Example 13, the first RRC message additionally indicates granularities of the respective time and frequency divisions.
[0150] [0150] Example 16. The UE, according to any of the previous Examples, in which each of the bits in the bitmap, indicates whether a downlink transmission to another UE is present in the corresponding portion of the time region -frequency.
[0151] [0151] Example 17. A method for wireless communications, comprising: transmitting, through a base station (BS) to a user equipment (UE), a first signal through the first resources assigned to bear link transmissions downward; and transmitting, through the BS to the UE, a first downlink control indication (DCI) message, the first DCI message comprises a bitmap that includes bits associated with different portions of a time-frequency region, and each of the bits in the bitmap indicates whether a downlink transmission to the UE is present in the corresponding portion of the time-frequency region, where the bits in the bitmap comprise a sequence of groups of bits time-splitting bits that correspond to different time splits, each of the time-splitting bit groups includes one or more bits, the one or more bits, in each of the time-splitting bit groups, correspond to one or more frequency divisions, and the one or more bits, in each of the time division bit groups, correspond to the same time division.
[0152] [0152] Example 18. The method, according to Example 17, in which the bits included in the bitmap are consecutive bits, and each of the time division bit groups includes two or more consecutive bits.
[0153] [0153] Example 19. The method, according to any of the previous Examples, in which each of the time division bit groups comprises a first bit and a second bit, the first bit corresponds to a first frequency division , and the second bit corresponds to a last frequency division.
[0154] [0154] Example 20. Method, according to Example 19, in which the first bit, in each of the time division bit groups, corresponds to the same first frequency division, and the second bit, in each one of the time division bit groups, corresponds to the same last frequency division.
[0155] [0155] Example 21. The method, according to any of the previous Examples, which further comprises: transmitting, via BS to the UE, a first radio resource control (RRC) message indicating a load size useful DCI message.
[0156] [0156] Example 22. The method, according to Example 21, the first RRC message additionally indicates the time-frequency region.
[0157] [0157] Example 23. The method, according to Example 21, the first RRC message additionally indicates granularities of the respective time and frequency divisions.
[0158] [0158] Example 24. The method, according to any of the previous Examples, in which each of the bits in the bitmap, indicates whether a preemptive downlink transmission to another UE is present in the corresponding portion of the time-frequency.
[0159] [0159] Example 25. A base station (BS) configured for wireless communications, BS comprises: a non-transitory memory store that comprises instructions; and one or more processors in communication with the memory, where the one or more processors carry out the instructions to: transmit, to a user equipment (UE), a first signal through the first resources assigned to bear downlink transmissions; and transmitting a first downlink control indication (DCI) message to the UE, the first DCI message comprises a bitmap that includes bits associated with different portions of a time-frequency region, and each of the bits, in the bitmap, indicate whether a downlink transmission to the UE is present in the corresponding portion of the time-frequency region, where the bits in the bitmap comprise a sequence of time-splitting bit groups that corresponds to different time divisions, each of the time division bit groups includes one or more bits, the one or more bits, in each of the time division bit groups, correspond to one or more time divisions frequency, and the one or more bits, in each of the time division bit groups, correspond to the same time division.
[0160] [0160] Example 26. The BS, according to Example 25, in which the bits included in the bitmap are consecutive bits, and each of the time division bit groups includes two or more consecutive bits.
[0161] [0161] Example 27. The BS, according to any of the previous Examples, in which each of the time division bit groups comprises a first bit and a second bit, the first bit corresponds to a first frequency division , and the second bit corresponds to a last frequency division.
[0162] [0162] Example 28. The BS, according to Example 27, the first bit, in each of the time division bit groups, corresponds to the same first frequency division, and the second bit, in each one among the time division bit groups, it corresponds to the same last frequency division.
[0163] [0163] Example 29. BS, according to any of the previous Examples, in which the one or more processors additionally execute the instructions to: transmit to the UE a first radio resource control (RRC) message which indicates a payload size of the DCI message.
[0164] [0164] Example 30. The BS, according to Example 29, the first RRC message additionally indicates the time-frequency region.
[0165] [0165] Example 31. The BS, according to Example 29, the first RRC message additionally indicates granularities of the respective time and frequency divisions.
[0166] [0166] Example 32. The BS, according to any of the previous Examples, where each of the bits in the bitmap, indicates whether a downlink transmission to another UE is present in the corresponding portion of the time region -frequency.
[0167] [0167] Although the description has been described in detail, it should be understood that when resource allocation for latency-tolerant traffic overlaps resource allocation for low-latency traffic in the time and frequency domains, several changes, substitutions and changes may be made without departing from the spirit and scope of this disclosure, as defined by the attached claims. Furthermore, the scope of the disclosure is not intended to be limited to the particular modalities described in this document, since a person of ordinary skill in the art will promptly verify, from this disclosure, what processes, machines, manufacturing, material compositions, means, methods or stages, currently existing or to be developed later, may perform substantially the same function or achieve substantially the same result as the corresponding modalities described in this document. Consequently, the appended claims are intended to include, within its scope, such processes, machines, manufacture, compositions of matter, means, methods or stages.

权利要求:
Claims (48)
[1]
1. Method for wireless communications, comprising: receiving, by means of a user equipment (UE) from a base station (BS), a first signal through the first resources assigned to bear downlink transmissions; and receiving, through the UE from the BS, a first downlink control indication (DCI) message, the first DCI message comprises a bitmap that includes bits associated with different portions of a time-frequency region , and each of the bits in the bitmap indicates whether a downlink transmission to the UE is present in the corresponding portion of the time-frequency region, where the bits in the bitmap comprise a sequence of split bit groups of time corresponding to different time divisions, each of the time division bit groups includes one or more bits, the one or more bits in each of the time division bit groups correspond to one or more divisions frequency, and the one or more bits in each of the time division bit groups correspond to the same time division.
[2]
A method according to claim 1, wherein the bits included in the bitmap are consecutive bits, and each of the time division bit groups includes two or more consecutive bits.
[3]
Method according to any one of claims 1 to 2, wherein each of the groups of time-division bits comprises a first bit and a second bit, the first bit corresponds to a first frequency division, and the second bit corresponds to a last frequency division.
[4]
Method according to claim 3, the first bit in each of the time division bit groups corresponds to the same first frequency division, and the second bit in each of the time division bit groups time corresponds to the same last frequency division.
[5]
A method according to any one of claims 1 to 4, further comprising: receiving, via the UE from the BS, a first radio resource control (RRC) message that indicates a message payload size of DCI.
[6]
6. Method, according to claim 5, the first message of
RRC additionally indicates the time-frequency region.
[7]
Method according to any one of claims 5 to 6, the first RRC message further indicates granularities of the respective time and frequency divisions.
[8]
8. Method, according to any one of claims 5 to 7, the first RRC message additionally includes a temporary radio network identifier (RNTI) field.
[9]
A method according to any one of claims 1 to 8, wherein each of the bits in the bitmap indicates whether a preemptive downlink transmission to another UE is present in the corresponding portion of the time-frequency region.
[10]
Method according to any one of claims 1 to 9, further comprising receiving, through the UE, a higher layer configuration indication, the configuration indication configures the UE with a temporary radio network identifier (RNTI ).
[11]
11. User equipment (UE) configured for wireless communications, the UE comprising: a non-transitory memory store comprising instructions; and one or more processors in communication with the memory, in which the one or more processors execute the instructions to: receive, from a base station (BS), a first signal through the first resources assigned to carry downlink transmissions ; and receiving, from the BS, a first downlink control indication (DCI) message, the first DCI message comprises a bitmap that includes bits associated with different portions of a time-frequency region, and each between the bits in the bitmap indicates whether a downlink transmission to the UE is present in the corresponding portion of the time-frequency region, where the bits in the bitmap comprise a sequence of time-splitting bit groups at different time divisions, each of the time division bit groups includes one or more bits, the one or more bits in each of the time division bit groups correspond to one or more frequency divisions, and o one or more bits, in each of the time division bit groups, correspond to the same time division.
[12]
12. The UE according to claim 11, wherein the bits included in the bitmap are consecutive bits, and each of the time division bit groups includes two or more consecutive bits.
[13]
13. UE according to any one of claims 11 to 12, wherein each of the groups of time-division bits comprises a first bit and a second bit, the first bit corresponds to a first frequency division, and the second bit corresponds to a last frequency division.
[14]
14. UE, according to claim 13, the first bit in each of the time division bit groups corresponds to the same first frequency division, and the second bit in each of the time division bit groups time corresponds to the same last frequency division.
[15]
15. UE according to any one of claims 11 to 14, wherein the one or more processors additionally carry out instructions to: receive a first radio resource control (RRC) message that indicates a message payload size of DCI.
[16]
16. UE, according to claim 15, the first RRC message additionally indicates the time-frequency region.
[17]
17. UE, according to any one of claims 15 to 16, the first RRC message further indicates granularities of the respective time and frequency divisions.
[18]
18. UE, according to any one of claims 15 to 17, the first RRC message additionally includes a temporary radio network identifier (RNTI) field.
[19]
19. The method of any one of claims 11 to 18, wherein each of the bits in the bitmap indicates whether a preemptive downlink transmission to another UE is present in the corresponding portion of the time-frequency region.
[20]
20. Method according to any one of claims 11 to 19, further comprising receiving, through the UE, a higher layer configuration indication, the configuration indication configures the UE with a temporary radio network identifier (RNTI ).
[21]
21. Method for wireless communications, comprising:
transmitting, through a base station (BS) to a user equipment (UE), a first signal through the first resources allocated to bear downlink transmissions; and transmitting, through the BS to the UE, a first downlink control indication (DCI) message, the first DCI message comprises a bitmap that includes bits associated with different portions of a time-frequency region, and each of the bits in the bitmap indicates whether a downlink transmission to the UE is present in the corresponding portion of the time-frequency region, where the bits in the bitmap comprise a sequence of time-splitting bit groups corresponding to different time divisions, each of the time division bit groups includes one or more bits, the one or more bits in each of the time division bit groups correspond to one or more frequency divisions , and the one or more bits in each of the time division bit groups correspond to the same time division.
[22]
22. The method of claim 21, wherein the bits included in the bitmap are consecutive bits, and each of the time division bit groups includes two or more consecutive bits.
[23]
23. The method of any one of claims 21 to 22, wherein each of the groups of time-division bits comprises a first bit and a second bit, the first bit corresponds to a first frequency division, and the second bit corresponds to a last frequency division.
[24]
24. The method of claim 23, the first bit in each of the time division bit groups corresponds to the same first frequency division, and the second bit in each of the time division bit groups time corresponds to the same last frequency division.
[25]
25. The method of any one of claims 21 to 24, further comprising: transmitting, via BS to the UE, a first radio resource control (RRC) message that indicates a payload size of the DCI message .
[26]
26. Method, according to claim 25, the first RRC message further indicates the time-frequency region.
[27]
27. The method of any one of claims 25 to 26,
the first RRC message additionally indicates granularities of the respective time and frequency divisions.
[28]
28. Method, according to any one of claims 25 to 27, the first RRC message additionally includes a temporary radio network identifier (RNTI) field.
[29]
29. The method of any one of claims 21 to 28, wherein each of the bits in the bitmap indicates whether a preemptive downlink transmission to another UE is present in the corresponding portion of the time-frequency region.
[30]
30. The method of any one of claims 21 to 29, further comprising receiving, through the UE, a higher layer configuration indication, the configuration indication configures the UE with a temporary radio network identifier (RNTI ).
[31]
31. Base station (BS) configured for wireless communications, comprising: a non-transitory memory storage comprising instructions; and one or more processors in communication with the memory, where the one or more processors carry out the instructions to: transmit, to a user equipment (UE), a first signal through the first resources assigned to bear downlink transmissions; and transmitting a first downlink control indication (DCI) message to the UE, the first DCI message comprises a bitmap that includes bits associated with different portions of a time-frequency region, and each of the bits in the bitmap indicates whether a downlink transmission to the UE is present in the corresponding portion of the time-frequency region, where the bits in the bitmap comprise a sequence of time-splitting bit groups corresponding to different time divisions, each of the time division bit groups includes one or more bits, the one or more bits in each of the time division bit groups correspond to one or more frequency divisions, and the one or more bits in each of the time division bit groups correspond to the same time division.
[32]
32. BS, according to claim 31, wherein the bits included in the bitmap are consecutive bits, and each of the time division bit groups includes two or more consecutive bits.
[33]
33. BS according to any one of claims 31 to 32, wherein each of the groups of time-division bits comprises a first bit and a second bit, the first bit corresponds to a first frequency division, and the second bit corresponds to a last frequency division.
[34]
34. BS, according to claim 33, the first bit in each of the time division bit groups corresponds to the same first frequency division, and the second bit in each of the time division bit groups time corresponds to the same last frequency division.
[35]
35. BS according to any one of claims 31 to 34, wherein the one or more processors additionally carry out the instructions to: transmit to the UE a first radio resource control (RRC) message that indicates a size of payload of the DCI message.
[36]
36. BS, according to claim 35, the first RRC message further indicates the time-frequency region.
[37]
37. BS, according to any one of claims 35 to 36, the first RRC message further indicates granularities of the respective time and frequency divisions.
[38]
38. BS, according to any one of claims 36 to 37, the first RRC message additionally includes a temporary radio network identifier (RNTI) field.
[39]
39. The method of any one of claims 31 to 38, wherein each of the bits in the bitmap indicates whether a preemptive downlink transmission to another UE is present in the corresponding portion of the time-frequency region.
[40]
40. The method of any one of claims 31 to 39, further comprising receiving, through the UE, a higher layer configuration indication, the configuration indication configures the UE with a temporary radio network identifier (RNTI ).
[41]
41. User equipment (UE) comprising: a receiver to: receive, from a base station (BS), a first signal through the first resources allocated to bear downlink transmissions; and receiving, from the BS, a first downlink control indication (DCI) message, the first DCI message comprises a bitmap that includes bits associated with different portions of a time-frequency region, and each between the bits in the bitmap indicates whether a downlink transmission to the UE is present in the corresponding portion of the time-frequency region, where the bits in the bitmap comprise a sequence of time-splitting bit groups at different time divisions, each of the time division bit groups includes one or more bits, the one or more bits in each of the time division bit groups correspond to one or more frequency divisions, and o one or more bits in each of the time division bit groups correspond to the same time division.
[42]
42. Computer-readable media containing the same instructions that, when executed by a processor, cause user equipment (UE): to receive, from a base station (BS), a first signal through the first assigned resources to carry downlink transmissions; and receives, from the BS, a first downlink control indication (DCI) message, the first DCI message comprises a bitmap that includes bits associated with different portions of a time-frequency region, and each between the bits in the bitmap indicates whether a downlink transmission to the UE is present in the corresponding portion of the time-frequency region, where the bits in the bitmap comprise a sequence of time-splitting bit groups at different time divisions, each of the time division bit groups includes one or more bits, the one or more bits in each of the time division bit groups correspond to one or more frequency divisions, and o one or more bits in each of the time division bit groups correspond to the same time division.
[43]
43. User equipment (UE) comprising: means for receiving, from a base station (BS), a first signal through the first resources allocated to bear downlink transmissions; and means for receiving, from the BS, a first downlink control indication (DCI) message, the first DCI message comprises a bitmap that includes bits associated with different portions of a time-frequency region, and each of the bits in the bitmap indicates whether a downlink transmission to the UE is present in the corresponding portion of the time-frequency region, where the bits in the bitmap comprise a sequence of time-splitting bit groups corresponding to different time divisions, each of the time division bit groups includes one or more bits, the one or more bits in each of the time division bit groups correspond to one or more frequency divisions , and the one or more bits in each of the time division bit groups correspond to the same time division.
[44]
44. User equipment (UE) configured to perform method as defined in any of claims 1 to 10.
[45]
45. Base station (BS) comprising: a transmitter for: transmitting, to a user equipment (UE), a first signal through the first resources assigned to bear downlink transmissions; and transmitting a first downlink control indication (DCI) message to the UE, the first DCI message comprises a bitmap that includes bits associated with different portions of a time-frequency region, and each of the bits in the bitmap indicates whether a downlink transmission to the UE is present in the corresponding portion of the time-frequency region, where the bits in the bitmap comprise a sequence of time-splitting bit groups corresponding to different time divisions, each of the time division bit groups includes one or more bits, the one or more bits in each of the time division bit groups correspond to one or more frequency divisions, and the one or more bits in each of the time division bit groups correspond to the same time division.
[46]
46. Computer-readable media containing the same instructions as,
when executed by a processor, they cause a base station (BS) to transmit, to a user equipment (UE), a first signal through the first resources assigned to bear downlink transmissions; and transmits a first downlink control indication (DCI) message to the UE, the first DCI message comprises a bitmap that includes bits associated with different portions of a time-frequency region, and each of the bits in the bitmap indicates whether a downlink transmission to the UE is present in the corresponding portion of the time-frequency region, where the bits in the bitmap comprise a sequence of time-splitting bit groups corresponding to different time divisions, each of the time division bit groups includes one or more bits, the one or more bits in each of the time division bit groups correspond to one or more frequency divisions, and the one or more bits in each of the time division bit groups correspond to the same time division.
[47]
47. Base station (BS) comprising: means for transmitting, to a user equipment (UE), a first signal through first resources allocated to bear downlink transmissions; and means for transmitting a first downlink control indication (DCI) message to the UE, the first DCI message comprises a bitmap that includes bits associated with different portions of a time-frequency region, and each between the bits in the bitmap indicates whether a downlink transmission to the UE is present in the corresponding portion of the time-frequency region, where the bits in the bitmap comprise a sequence of time-splitting bit groups at different time divisions, each of the time division bit groups includes one or more bits, the one or more bits in each of the time division bit groups correspond to one or more frequency divisions, and o one or more bits in each of the time division bit groups correspond to the same time division.
[48]
48. Base station (BS) configured to carry out the method as defined in any of claims 21 to 30.

类似技术:

---

公开号 | 公开日 | 专利标题

---

BR112020002686A2|2020-07-28|system and method to enable low latency and reliable communication

---

JP6827528B2|2021-02-10|Systems and methods for multiplexing traffic

---

US20180279289A1|2018-09-27|System and Method for Signaling for Resource Allocation for One or More Numerologies

---

US9894651B2|2018-02-13|Methods and apparatus for resource allocation for D2D communications

---

ES2864022T3|2021-10-13|User terminal and radio communication method

---

BR112019019401A2|2020-05-05|methods and apparatus for notifying a eu of preemption

---

ES2893794T3|2022-02-10|User terminal and wireless communication method

---

US11218268B2|2022-01-04|User terminal and radio communication method

---

WO2019082247A1|2019-05-02|User terminal and radio communication method

---

JPWO2018030416A1|2019-06-27|User terminal and wireless communication method

---

WO2019077727A1|2019-04-25|User terminal and wireless communication method

---

EP3496487B1|2022-01-19|User equipment and radio communication method

---

JPWO2019021486A1|2020-07-09|User terminal, wireless base station, and wireless communication method

---

WO2019049283A1|2019-03-14|User terminal and radio communication method

---

JPWO2019016953A1|2020-07-16|User terminal and wireless communication method

---

KR20190123761A|2019-11-01|User terminal and wireless communication method

---

JPWO2019021487A1|2020-07-09|User terminal and wireless communication method

---

JPWO2018025948A1|2019-06-06|User terminal and wireless communication method

---

US10999763B2|2021-05-04|User terminal and radio communication method

---

WO2019073968A1|2019-04-18|User equipment and wireless communication method

---

WO2019030871A1|2019-02-14|User terminal and radio communication method

---

WO2019053902A1|2019-03-21|User terminal and radio communication method

---

WO2019030869A1|2019-02-14|User terminal, base station, and radio communication method

---

JPWO2018012457A1|2019-05-16|User terminal and wireless communication method

---

WO2019097702A1|2019-05-23|User terminal and wireless communication method

同族专利:

---

公开号 | 公开日

---

KR20200034797A|2020-03-31|

---

EP3666011A1|2020-06-17|

---

RU2020109707A3|2021-12-17|

---

AU2018315101A1|2020-03-12|

---

US20200389274A1|2020-12-10|

---

EP3666011B1|2021-10-27|

---

US20190052432A1|2019-02-14|

---

KR102288179B1|2021-08-09|

---

RU2020109707A|2021-09-10|

---

AU2018315101B2|2021-04-01|

---

CN111034313A|2020-04-17|

---

JP2020530960A|2020-10-29|

---

EP3666011A4|2020-08-19|

---

US10728002B2|2020-07-28|

---

WO2019029585A1|2019-02-14|

引用文献:

---

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

---

---

US8767637B2|2007-11-05|2014-07-01|Apple Inc.|Methods and systems for resource allocation|

---

JP5072999B2|2010-04-05|2012-11-14|株式会社エヌ・ティ・ティ・ドコモ|Wireless communication control device and wireless communication control method|

---

US9515787B2|2012-05-11|2016-12-06|Nokia Solutions And Networks Oy|Wireless communication scheduling on shared spectra|

---

US9386602B2|2013-09-20|2016-07-05|Blackberry Limited|Method and system for HARQ operation and scheduling in joint TDD and FDD carrier aggregation|

---

WO2015152581A1|2014-03-30|2015-10-08|엘지전자|Method for transmitting/receiving downlink control information in wireless communication system supporting device-to-device communication and apparatus therefor|

---

CN105099634B|2014-05-09|2019-05-07|中兴通讯股份有限公司|Distribution method and device, base station, the terminal of dynamic resource|

---

CN105323049A|2014-06-13|2016-02-10|中兴通讯股份有限公司|Scheduling method, device and system of unauthorized carrier|

---

US20160135056A1|2014-11-06|2016-05-12|Htc Corporation|Device of Handling Measurement Signal on Unlicensed Carrier|

---

US10104683B2|2015-02-06|2018-10-16|Qualcomm Incorporated|Parallel low latency awareness|

---

US20180027576A1|2016-07-21|2018-01-25|Sharp Laboratories Of America, Inc.|User equipment and base stations that transceive ultra reliable low latency messages amidst delay tolerant transceptions|

---

WO2018021834A1|2016-07-29|2018-02-01|Samsung Electronics Co., Ltd.|Method and apparatus for handling collisions in next generation communication system|

---

US20180035459A1|2016-07-29|2018-02-01|Huawei Technologies Co., Ltd.|Coexistence of Grant-Based and Grant-Free Uplink Transmissions in a Channel|

---

US11071136B2|2016-08-25|2021-07-20|Huawei Technologies Co., Ltd.|System and method for multiplexing traffic|

---

US11252717B2|2016-09-02|2022-02-15|Huawei Technologies Co., Ltd.|Co-existence of latency tolerant and low latency communications|

---

CN109804657A|2016-09-28|2019-05-24|Idac控股公司|For the 5G NR data transmission of agile radio service|

---

WO2018093103A1|2016-11-15|2018-05-24|엘지전자 주식회사|Method for transmitting information regarding available resource, and apparatus therefor|

---

US10869303B2|2017-03-16|2020-12-15|Kt Corporation|Method for monitoring, transmitting, and receiving downlink pre-emption indication information in new radio networks and apparatus thereof|

---

US10609699B2|2017-03-16|2020-03-31|Kt Corporation|Method for monitoring, transmitting, and receiving downlink pre-emption indication information in new radio networks and apparatus thereof|

---

US10856307B2|2017-03-21|2020-12-01|Kt Corporation|Method for transmitting and receiving downlink pre-emption indication information using bitmap in new radio networks and apparatus thereof|

---

US10567142B2|2017-03-23|2020-02-18|Apple Inc.|Preemption indicators and code-block-group-based retransmission techniques for multiplexing different services on physical layer frames|

---

US11115257B2|2017-03-23|2021-09-07|Huawei Technologies Co., Ltd.|System and method for multiplexing traffic|

---

US10863522B2|2017-05-03|2020-12-08|Huawei Technologies Co., Ltd.|System and method for coexistence of low latency and latency tolerant communications|

---

CN107294667B|2017-06-16|2020-11-10|宇龙计算机通信科技有限公司|Data receiving and transmitting configuration method and related device|

---

US10873934B2|2017-09-28|2020-12-22|Ofinno, Llc|Pre-emption indication in a wireless device|

---

US10979988B2|2017-11-07|2021-04-13|Apple Inc.|Methods of limited buffer rate-matching , pre-emption, and sidelink synchronization in new radio systems|

---

US11032032B2|2017-11-28|2021-06-08|Qualcomm Incorporated|Sub-band configuration for preemption indication to eMBB UEs|

---

KR20190097698A|2018-02-13|2019-08-21|삼성전자주식회사|A method and apparatus for transmission and reception of data and control information in wireless communication system|

---

US20190254081A1|2018-02-14|2019-08-15|Qualcomm Incorporated|Uplink and downlink preemption indications|

---

EP3547780B1|2018-03-30|2022-02-16|Comcast Cable Communications LLC|Wireless communications for uplink preemption and downlink preemption|JP6911296B2|2016-08-08|2021-07-28|ソニーグループ株式会社|Communication equipment, communication methods, and programs|

---

WO2019050451A1|2017-09-11|2019-03-14|Telefonaktiebolaget Lm Ericsson |Preemption indication for new radio|

---

US10873934B2|2017-09-28|2020-12-22|Ofinno, Llc|Pre-emption indication in a wireless device|

---

US10945251B2|2017-11-15|2021-03-09|Sharp Kabushiki Kaisha|User equipments, base stations and methods|

---

US10945172B2|2017-11-16|2021-03-09|Comcast Cable Communications, Llc|Power control for bandwidth part switching|

---

US10448388B2|2018-01-11|2019-10-15|Lg Electronics Inc.|Method for receiving downlink signal in wireless communication system and terminal using the same|

---

KR101954433B1|2018-01-11|2019-03-05|엘지전자 주식회사|A method of receiving a downlink signal for a terminal in a wireless communication system and a terminal using the same|

---

US11044135B2|2018-01-23|2021-06-22|Qualcomm Incorporated|NR-SS LBT gap optimizations|

---

US11006442B2|2018-02-13|2021-05-11|Mediatek Singapore Pte. Ltd.|Method and apparatus for bandwidth part switch operations in mobile communications|

---

US11234253B2|2018-09-28|2022-01-25|Qualcomm Incorporated|Transmit parameter control|

---

CN111277384B|2019-02-27|2021-09-14|维沃移动通信有限公司|Transmission resource indication method, transmission method, network equipment and terminal|

---

US11239939B2|2019-03-22|2022-02-01|Samsung Electronics Co., Ltd.|Scheduling in communication systems with multiple service types|

---

CN113906709A|2019-04-02|2022-01-07|苹果公司|Method for enhanced PDCCH monitoring|

---

CN111867118A|2019-04-30|2020-10-30|华为技术有限公司|Resource scheduling method and communication device|

---

US11258540B2|2019-07-19|2022-02-22|Cisco Technology, Inc.|Ultra-reliability for cellular vehicle-to-everythingPC5 communications|

---

WO2021217478A1|2020-04-29|2021-11-04|Qualcomm Incorporated|Method of configuring group common dci for mu-mimo|

---

WO2021226996A1|2020-05-15|2021-11-18|Qualcomm Incorporated|Refraining from monitoring physical downlink control channelrepetition monitoring occasions|

法律状态:
2021-11-03| B350| Update of information on the portal [chapter 15.35 patent gazette]|

优先权:

---

申请号 | 申请日 | 专利标题

---

US201762543825P| true| 2017-08-10|2017-08-10|

---

US62/543,825|2017-08-10|

---

US15/925,452|US10728002B2|2017-08-10|2018-03-19|System and method for enabling reliable and low latency communication|

---

US15/925,452|2018-03-19|

---

PCT/CN2018/099486|WO2019029585A1|2017-08-10|2018-08-09|System and method for enabling reliable and low latency communication|

---